Systems and methods for signaling video parameter information in video coding

ABSTRACT

A method of decoding video data includes: receiving a video parameter set; parsing a first syntax element in the video parameter set, wherein the first syntax element plus one specifies a maximum allowed number of layers in each coded video sequence referring to the video parameter set; and parsing a second syntax element in the video parameter set, in a case that a value of the first syntax element is greater than a threshold value, wherein the second syntax element plus one specifies a number of profile tier level syntax structure in the video parameter set.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims priority from Provisional Application Nos. 63/021,019 and 63/035,740, the contents of which are hereby incorporated by reference into this application.

TECHNICAL FIELD

This disclosure relates to video coding and more particularly to techniques for signaling video parameter information for coded video.

BACKGROUND

Digital video capabilities can be incorporated into a wide range of devices, including digital televisions, laptop or desktop computers, tablet computers, digital recording devices, digital media players, video gaming devices, cellular telephones, including so-called smartphones, medical imaging devices, and the like. Digital video may be coded according to a video coding standard. Video coding standards define the format of a compliant bitstream encapsulating coded video data. A compliant bitstream is a data structure that may be received and decoded by a video decoding device to generate reconstructed video data. Video coding standards may incorporate video compression techniques. Examples of video coding standards include ISO/IEC MPEG-4 Visual and ITU-T H.264 (also known as ISO/IEC MPEG-4 AVC) and High-Efficiency Video Coding (HEVC). HEVC is described in High Efficiency Video Coding (HEVC), Rec. ITU-T H.265, December 2016, which is incorporated by reference, and referred to herein as ITU-T H.265. Extensions and improvements for ITU-T H.265 are currently being considered for the development of next generation video coding standards. For example, the ITU-T Video Coding Experts Group (VCEG) and ISO/IEC (Moving Picture Experts Group (MPEG) (collectively referred to as the Joint Video Exploration Team (JVET)) are working to standardized video coding technology with a compression capability that significantly exceeds that of the current HEVC standard. The Joint Exploration Model 7 (JEM 7), Algorithm Description of Joint Exploration Test Model 7 (JEM 7). ISO/IEC JTC1/SC29/WG11 Document: JVET-G1001, July 2017, Torino, IT, which is incorporated by reference herein, describes the coding features that were under coordinated test model study by the JVET as potentially enhancing video coding technology beyond the capabilities of ITU-T H.265. It should be noted that the coding features of JEM 7 are implemented in JEM reference software. As used herein, the term JEM may collectively refer to algorithms included in JEM 7 and implementations of JEM reference software. Further, in response to a “Joint Call for Proposals on Video Compression with Capabilities beyond HEVC,” jointly issued by VCEG and MPEG, multiple descriptions of video coding tools were proposed by various groups at the 10^(th) Meeting of ISO/IEC JTC1/SC29/WG11 16-20 Apr. 2018, San Diego, Calif. From the multiple descriptions of video coding tools, a resulting initial draft text of a video coding specification is described in “Versatile Video Coding (Draft 1).” 10^(th) Meeting of ISO/IEC JTC1/SC29/WG11 16-20 Apr. 2018, San Diego, Calif., document JVET-J1001-v2, which is incorporated by reference herein, and referred to as JVET-J1001. The current development of a next generation video coding standard by the VCEG and MPEG is referred to as the Versatile Video Coding (VVC) project. “Versatile Video Coding (Draft 9).” 18th Meeting of ISO/IEC JTC1/SC29/WG11 15-24 Apr. 2020, Teleconference, document JVET-R2001-v7, which is incorporated by reference herein, and referred to as JVET-R2001, represents the current iteration of the draft text of a video coding specification corresponding to the VVC project.

Video compression techniques enable data requirements for storing and transmitting video data to be reduced. Video compression techniques may reduce data requirements by exploiting the inherent redundancies in a video sequence. Video compression techniques may sub-divide a video sequence into successively smaller portions (i.e., groups of pictures within a video sequence, a picture within a group of pictures, regions within a picture, sub-regions within regions, etc.). Intra prediction coding techniques (e.g., spatial prediction techniques within a picture) and inter prediction techniques (i.e., inter-picture techniques (temporal)) may be used to generate difference values between a unit of video data to be coded and a reference unit of video data. The difference values may be referred to as residual data. Residual data may be coded as quantized transform coefficients. Syntax elements may relate residual data and a reference coding unit (e.g., intra-prediction mode indices, and motion information). Residual data and syntax elements may be entropy coded. Entropy encoded residual data and syntax elements may be included in data structures forming a compliant bitstream.

SUMMARY

In general, this disclosure describes various techniques for coding video data. In particular, this disclosure describes techniques for signaling video parameter information for coded video data. It should be noted that although techniques of this disclosure are described with respect to ITU-T H.264, ITU-T H.265, JEM, and JVET-R2001, the techniques of this disclosure are generally applicable to video coding. For example, the coding techniques described herein may be incorporated into video coding systems, (including video coding systems based on future video coding standards) including video block structures, intra prediction techniques, inter prediction techniques, transform techniques, filtering techniques, and/or entropy coding techniques other than those included in ITU-T H.265, JEM, and JVET-R2001. Thus, reference to ITU-T H.264, ITU-T H.265, JEM, and/or JVET-R2001 is for descriptive purposes and should not be construed to limit the scope of the techniques described herein. Further, it should be noted that incorporation by reference of documents herein is for descriptive purposes and should not be construed to limit or create ambiguity with respect to terms used herein. For example, in the case where an incorporated reference provides a different definition of a term than another incorporated reference and/or as the term is used herein, the term should be interpreted in a manner that broadly includes each respective definition and/or in a manner that includes each of the particular definitions in the alternative.

In one example, a method of decoding video data includes: receiving a video parameter set; parsing a first syntax element in the video parameter set, wherein the first syntax element plus one specifies a maximum allowed number of layers in each coded video sequence referring to the video parameter set; and parsing a second syntax element in the video parameter set, in a case that a value of the first syntax element is greater than a threshold value, wherein the second syntax element plus one specifies a number of profile tier level syntax structure in the video parameter seta method of decoding video data, the method comprises.

In one example, the method includes parsing a third syntax element in the video parameter set, wherein the third syntax element plus two specifies a total number of output layer sets specified by the video parameter set.

In one example, a device includes one or more processors configured to: receive a video parameter set; parse a first syntax element in the video parameter set, wherein the first syntax element plus one specifies a maximum allowed number of layers in each coded video sequence referring to the video parameter set; and parse a second syntax element in the video parameter set, in a case that a value of the first syntax element is greater than a threshold value, wherein the second syntax element plus one specifies a number of profile tier level syntax structure in the video parameter set.

In one example, a method of encoding image data includes signaling a video parameter set. The video parameter set includes (i) a first syntax element, wherein the first syntax element plus one specifies a maximum allowed number of layers in each coded video sequence referring to the video parameter set and (ii) a second syntax element, wherein the second syntax element plus one specifies a number of profile tier level syntax structure in the video parameter set. The second syntax element is included, in a case that a value of the first syntax element is greater than a threshold value.

The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example of a system that may be configured to encode and decode video data according to one or more techniques of this disclosure.

FIG. 2 is a conceptual diagram illustrating coded video data and corresponding data structures according to one or more techniques of this disclosure.

FIG. 3 is a conceptual diagram illustrating a data structure encapsulating coded video data and corresponding metadata according to one or more techniques of this disclosure.

FIG. 4 is a conceptual drawing illustrating an example of components that may be included in an implementation of a system that may be configured to encode and decode video data according to one or more techniques of this disclosure.

FIG. 5 is a block diagram illustrating an example of a video encoder that may be configured to encode video data according to one or more techniques of this disclosure.

FIG. 6 is a block diagram illustrating an example of a video decoder that may be configured to decode video data according to one or more techniques of this disclosure.

DETAILED DESCRIPTION

Video content includes video sequences comprised of a series of frames (or pictures). A series of frames may also be referred to as a group of pictures (GOP). Each video frame or picture may divided into one or more regions. Regions may be defined according to a base unit (e.g., a video block) and sets of rules defining a region. For example, a rule defining a region may be that a region must be an integer number of video blocks arranged in a rectangle. Further, video blocks in a region may be ordered according to a scan pattern (e.g., a raster scan). As used herein, the term video block may generally refer to an area of a picture or may more specifically refer to the largest array of sample values that may be predictively coded, sub-divisions thereof, and/or corresponding structures. Further, the term current video block may refer to an area of a picture being encoded or decoded. A video block may be defined as an array of sample values. It should be noted that in some cases pixel values may be described as including sample values for respective components of video data, which may also be referred to as color components, (e.g., luma (Y) and chroma (Cb and Cr) components or red, green, and blue components). It should be noted that in some cases, the terms pixel value and sample value are used interchangeably. Further, in some cases, a pixel or sample may be referred to as a pel. A video sampling format, which may also be referred to as a chroma format, may define the number of chroma samples included in a video block with respect to the number of luma samples included in a video block. For example, for the 4:2:0 sampling format, the sampling rate for the luma component is twice that of the chroma components for both the horizontal and vertical directions.

A video encoder may perform predictive encoding on video blocks and sub-divisions thereof. Video blocks and sub-divisions thereof may be referred to as nodes. ITU-T H.264 specifies a macroblock including 16×16 luma samples. That is, in ITU-T H.264, a picture is segmented into macroblocks. ITU-T H.265 specifies an analogous Coding Tree Unit (CTU) structure (which may be referred to as a largest coding unit (LCU)). In ITU-T H.265, pictures are segmented into CTUs. In ITU-T H.265, for a picture, a CTU size may be set as including 16×16, 32×32, or 64×64 luma samples. In ITU-T H.265, a CTU is composed of respective Coding Tree Blocks (CTB) for each component of video data (e.g., luma (Y) and chroma (Cb and Cr). It should be noted that video having one luma component and the two corresponding chroma components may be described as having two channels. i.e., a luma channel and a chroma channel. Further, in ITU-T H.265, a CTU may be partitioned according to a quadtree (QT) partitioning structure, which results in the CTBs of the CTU being partitioned into Coding Blocks (CB). That is, in ITU-T H.265, a CTU may be partitioned into quadtree leafnodes. According to ITU-T H.265, one luma CB together with two corresponding chroma CBs and associated syntax elements are referred to as a coding unit (CU). In ITU-T H.265, a minimum allowed size of a CB may be signaled. In ITU-T H.265, the smallest minimum allowed size of a luma CB is 8×8 luma samples. In ITU-T H.265, the decision to code a picture area using intra prediction or inter prediction is made at the CU level.

In ITU-T H.265, a CU is associated with a prediction unit structure having its root at the CU. In ITU-T H.265, prediction unit structures allow luma and chroma CBs to be split for purposes of generating corresponding reference samples. That is, in ITU-T H.265, luma and chroma CBs may be split into respective luma and chroma prediction blocks (PBs), where a PB includes a block of sample values for which the same prediction is applied. In ITU-T H.265, a CB may be partitioned into 1, 2, or 4 PBs. ITU-T H.265 supports PB sizes from 64×64 samples down to 4×4 samples. In ITU-T H.265, square PBs are supported for intra prediction, where a CB may form the PB or the CB may be split into four square PBs. In ITU-T H.265, in addition to the square PBs, rectangular PBs are supported for inter prediction, where a CB may be halved vertically or horizontally to form PBs. Further, it should be noted that in ITU-T H.265, for inter prediction, four asymmetric PB partitions are supported, where the CB is partitioned into two PBs at one quarter of the height (at the top or the bottom) or width (at the left or the right) of the CB. Intra prediction data (e.g., intra prediction mode syntax elements) or inter prediction data (e.g., motion data syntax elements) corresponding to a PB is used to produce reference and/or predicted sample values for the PB.

JEM specifies a CTU having a maximum size of 256×256 luma samples. JEM specifies a quadtree plus binary tree (QTBT) block structure. In JEM, the QTBT structure enables quadtree leaf nodes to be further partitioned by a binary tree (BT) structure. That is, in JEM, the binary tree structure enables quadtree leaf nodes to be recursively divided vertically or horizontally. In JVET-R2001, CTUs are partitioned according a quadtree plus multi-type tree (QTMT or QT+MTT) structure. The QTMT in JVET-R2001 is similar to the QTBT in JEM. However, in JVET-R2001, in addition to indicating binary splits, the multi-type tree may indicate so-called ternary (or triple tree (TT)) splits. A ternary split divides a block vertically or horizontally into three blocks. In the case of a vertical TT split, a block is divided at one quarter of its width from the left edge and at one quarter its width from the right edge and in the case of a horizontal TT split a block is at one quarter of its height from the top edge and at one quarter of its height from the bottom edge.

As described above, each video frame or picture may be divided into one or more regions. For example, according to ITU-T H.265, each video frame or picture may be partitioned to include one or more slices and further partitioned to include one or more tiles, where each slice includes a sequence of CTUs (e.g., in raster scan order) and where a tile is a sequence of CTUs corresponding to a rectangular area of a picture. It should be noted that a slice, in ITU-T H.265, is a sequence of one or more slice segments starting with an independent slice segment and containing all subsequent dependent slice segments (if any) that precede the next independent slice segment (if any). A slice segment, like a slice, is a sequence of CTUs. Thus, in some cases, the terms slice and slice segment may be used interchangeably to indicate a sequence of CTUs arranged in a raster scan order. Further, it should be noted that in ITU-T H.265, a tile may consist of CTUs contained in more than one slice and a slice may consist of CT Us contained in more than one tile. However, ITU-T H.265 provides that one or both of the following conditions shall be fulfilled: (1) All CTUs in a slice belong to the same tile; and (2) All CTUs in a tile belong to the same slice.

With respect to JVET-R2001, slices are required to consist of an integer number of complete tiles or an integer number of consecutive complete CTU rows within a tile, instead of only being required to consist of an integer number of CTUs. It should be noted that in JVET-R2001, the slice design does not include slice segments (i.e., no independent/dependent slice segments). Thus, in JVET-R2001, a picture may include a single tile, where the single tile is contained within a single slice or a picture may include multiple tiles where the multiple tiles (or CTU rows thereof) may be contained within one or more slices. In JVET-R2001, the partitioning of a picture into tiles is specified by specifying respective heights for tile rows and respective widths for tile columns. Thus, in JVET-R2001 a tile is a rectangular region of CTUs within a particular tile row and a particular tile column position. Further, it should be noted that JVET-R2001 provides where a picture may be partitioned into subpictures, where a subpicture is a rectangular region of a CTUs within a picture. The top-left CTU of a subpicture may be located at any CTU position within a picture with subpictures being constrained to include one or more slices Thus, unlike a tile, a subpicture is not necessarily limited to a particular row and column position. It should be noted that subpictures may be useful for encapsulating regions of interest within a picture and a sub-bitstream extraction process may be used to only decode and display a particular region of interest. That is, as described in further detail below, a bitstream of coded video data includes a sequence of network abstraction layer (NAL) units, where a NAL unit encapsulates coded video data, (i.e., video data corresponding to a slice of picture) or a NAL unit encapsulates metadata used for decoding video data (e.g., a parameter set) and a sub-bitstream extraction process forms a new bitstream by removing one or more NAL units from a bitstream.

FIG. 2 is a conceptual diagram illustrating an example of a picture within a group of pictures partitioned according to tiles, slices, and subpictures. It should be noted that the techniques described herein may be applicable to tiles, slices, subpictures, sub-divisions thereof and/or equivalent structures thereto. That is, the techniques described herein may be generally applicable regardless of how a picture is partitioned into regions. For example, in some cases, the techniques described herein may be applicable in cases where a tile may be partitioned into so-called bricks, where a brick is a rectangular region of CTU rows within a particular tile. Further, for example, in some cases, the techniques described herein may be applicable in cases where one or more tiles may be included in so-called tile groups, where a tile group includes an integer number of adjacent tiles. In the example illustrated in FIG. 2. Pic₃ is illustrated as including 16 tiles (i.e., Tile₀ to Tile₁₅) and three slices (i.e., Slice₀ to Slice₂). In the example illustrated in FIG. 2, Slice₀ includes four tiles (i.e., Tile₀ to Tile₃). Slice₁ includes eight tiles (i.e., Tile₄ to Tile₁₁), and Slice₂ includes four tiles (i.e., Tile₁₂ to Tile₁₅). Further, as illustrated in the example of FIG. 2, Pic₃ is illustrated as including two subpictures (i.e., Subpicture₀ and Subpicture₁), where Subpicture₀ includes Slice₀ and Slice₁ and where Subpicture₁ includes Slice₂. As described above, subpictures may be useful for encapsulating regions of interest within a picture and a sub-bitstream extraction process may be used in order to selectively decode (and display) a region interest. For example, referring to FIG. 2. Subpicture₀ may corresponding to an action portion of a sporting event presentation (e.g., a view of the field) and Subpicture₁ may corresponding to a scrolling banner displayed during the sporting event presentation. By using organizing a picture into subpictures in this manner, a viewer may be able to disable the display of the scrolling banner. That is, through a sub-bitstream extraction process Slice₂ NAL unit may be removed from a bitstream (and thus not decoded and/or displayed) and Slice₀ NAL unit and Slice₁ NAL unit may be decoded and displayed. The encapsulation of slices of a picture into respective NAL unit data structures and sub-bitstream extraction are described in further detail below.

For intra prediction coding, an intra prediction mode may specify the location of reference samples within a picture. In ITU-T H.265, defined possible intra prediction modes include a planar (i.e., surface fitting) prediction mode, a DC (i.e., flat overall averaging) prediction mode, and 33 angular prediction modes (predMode: 2-34). In JEM, defined possible intra-prediction modes include a planar prediction mode, a DC prediction mode, and 65 angular prediction modes. It should be noted that planar and DC prediction modes may be referred to as non-directional prediction modes and that angular prediction modes may be referred to as directional prediction modes. It should be noted that the techniques described herein may be generally applicable regardless of the number of defined possible prediction modes.

For inter prediction coding, a reference picture is determined and a motion vector (MV) identifies samples in the reference picture that are used to generate a prediction for a current video block. For example, a current video block may be predicted using reference sample values located in one or more previously coded picture(s) and a motion vector is used to indicate the location of the reference block relative to the current video block. A motion vector may describe, for example, a horizontal displacement component of the motion vector (i.e., MV_(x)), a vertical displacement component of the motion vector (i.e., MV_(y)), and a resolution for the motion vector (e.g., one-quarter pixel precision, one-half pixel precision, one-pixel precision, two-pixel precision, four-pixel precision). Previously decoded pictures, which may include pictures output before or after a current picture, may be organized into one or more to reference pictures lists and identified using a reference picture index value. Further, in inter prediction coding, uni-prediction refers to generating a prediction using sample values from a single reference picture and bi-prediction refers to generating a prediction using respective sample values from two reference pictures. That is, in uni-prediction, a single reference picture and corresponding motion vector are used to generate a prediction for a current video block and in bi-prediction, a first reference picture and corresponding first motion vector and a second reference picture and corresponding second motion vector are used to generate a prediction for a current video block. In bi-prediction, respective sample values are combined (e.g., added, rounded, and clipped, or averaged according to weights) to generate a prediction. Pictures and regions thereof may be classified based on which types of prediction modes may be utilized for encoding video blocks thereof. That is, for regions having a B type (e.g., a B slice), bi-prediction, uni-prediction, and intra prediction modes may be utilized, for regions having a P type (e.g., a P slice), uni-prediction, and intra prediction modes may be utilized, and for regions having an I type (e.g., an I slice), only intra prediction modes may be utilized. As described above, reference pictures are identified through reference indices. For example, for a P slice, there may be a single reference picture list, RefPicList0 and for a B slice, there may be a second independent reference picture list. RefPicList1, in addition to RefPicList0. It should be noted that for uni-prediction in a B slice, one of RefPicList0 or RefPicList1 may be used to generate a prediction. Further, it should be noted that during the decoding process, at the onset of decoding a picture, reference picture list(s) are generated from previously decoded pictures stored in a decoded picture buffer (DPB).

Further, a coding standard may support various modes of motion vector prediction. Motion vector prediction enables the value of a motion vector for a current video block to be derived based on another motion vector. For example, a set of candidate blocks having associated motion information may be derived from spatial neighboring blocks and temporal neighboring blocks to the current video block. Further, generated (or default) motion information may be used for motion vector prediction. Examples of motion vector prediction include advanced motion vector prediction (AMVP), temporal motion vector prediction (TMVP), so-called “merge” mode, and “skip” and “direct” motion inference. Further, other examples of motion vector prediction include advanced temporal motion vector prediction (ATMVP) and Spatial-temporal motion vector prediction (STMVP). For motion vector prediction, both a video encoder and video decoder perform the same process to derive a set of candidates. Thus, for a current video block, the same set of candidates is generated during encoding and decoding.

As described above, for inter prediction coding, reference samples in a previously coded picture are used for coding video blocks in a current picture. Previously coded pictures which are available for use as reference when coding a current picture are referred as reference pictures. It should be noted that the decoding order does not necessary correspond with the picture output order, i.e., the temporal order of pictures in a video sequence. In ITU-T H.265, when a picture is decoded it is stored to a decoded picture buffer (DPB) (which may be referred to as frame buffer, a reference buffer, a reference picture buffer, or the like). In ITU-T H.265, pictures stored to the DPB are removed from the DPB when they been output and are no longer needed for coding subsequent pictures. In ITU-T H.265, a determination of whether pictures should be removed from the DPB is invoked once per picture, after decoding a slice header. i.e., at the onset of decoding a picture. For example, referring to FIG. 2, Pic₂ is illustrated as referencing Pic₁. Similarly. Pic₃ is illustrated as referencing Pic₀. With respect to FIG. 2, assuming the picture number corresponds to the decoding order, the DPB would be populated as follows: after decoding Pic₀, the DPB would include {Pic₀}; at the onset of decoding Pic₁, the DPB would include {Pic₀}; after decoding Pic₁, the DPB would include {Pic₀, Pic₁}; at the onset of decoding Pic₂, the DPB would include {Pic₀, Pic₁}. Pic₂ would then be decoded with reference to Pic₁ and after decoding Pic₂, the DPB would include {Pic₀, Pic₁, Pic₂}. At the onset of decoding Pic₃, pictures Pic₀ and Pic₁ would be marked for removal from the DPB, as they are not needed for decoding Pic₃ (or any subsequent pictures, not shown) and assuming Pic₁ and Pic₂ have been output, the DPB would be updated to include {Pic₀}. Pic₃ would then be decoded by referencing Pic₀. The process of marking pictures for removal from a DPB may be referred to as reference picture set (RPS) management.

As described above, intra prediction data or inter prediction data is used to produce reference sample values for a block of sample values. The difference between sample values included in a current PB, or another type of picture area structure, and associated reference samples (e.g., those generated using a prediction) may be referred to as residual data. Residual data may include respective arrays of difference values corresponding to each component of video data. Residual data may be in the pixel domain. A transform, such as, a discrete cosine transform (DCT), a discrete sine transform (DST), an integer transform, a wavelet transform, or a conceptually similar transform, may be applied to an array of difference values to generate transform coefficients. It should be noted that in ITU-T H.265 and JVET-R2001, a CU is associated with a transform tree structure having its root at the CU level. The transform tree is partitioned into one or more transform units (TUs). That is, an array of difference values may be partitioned for purposes of generating transform coefficients (e.g., four 8×8 transforms may be applied to a 16×16 array of residual values). For each component of video data, such sub-divisions of difference values may be referred to as Transform Blocks (TBs). It should be noted that in some cases, a core transform and subsequent secondary transforms may be applied (in the video encoder) to generate transform coefficients. For a video decoder, the order of transforms is reversed.

A quantization process may be performed on transform coefficients or residual sample values directly (e.g., in the case, of palette coding quantization). Quantization approximates transform coefficients by amplitudes restricted to a set of specified values. Quantization essentially scales transform coefficients in order to vary the amount of data required to represent a group of transform coefficients. Quantization may include division of transform coefficients (or values resulting from the addition of an offset value to transform coefficients) by a quantization scaling factor and any associated rounding functions (e.g., rounding to the nearest integer). Quantized transform coefficients may be referred to as coefficient level values. Inverse quantization (or “dequantization”) may include multiplication of coefficient level values by the quantization scaling factor, and any reciprocal rounding or offset addition operations. It should be noted that as used herein the term quantization process in some instances may refer to division by a scaling factor to generate level values and multiplication by a scaling factor to recover transform coefficients in some instances. That is, a quantization process may refer to quantization in some cases and inverse quantization in some cases. Further, it should be noted that although in some of the examples below quantization processes are described with respect to arithmetic operations associated with decimal notation, such descriptions are for illustrative purposes and should not be construed as limiting. For example, the techniques described herein may be implemented in a device using binary operations and the like. For example, multiplication and division operations described herein may be implemented using bit shifting operations and the like.

Quantized transform coefficients and syntax elements (e.g., syntax elements indicating a coding structure for a video block) may be entropy coded according to an entropy coding technique. An entropy coding process includes coding values of syntax elements using lossless data compression algorithms. Examples of entropy coding techniques include content adaptive variable length coding (CAVLC), context adaptive binary arithmetic coding (CABAC), probability interval partitioning entropy coding (PIPE), and the like. Entropy encoded quantized transform coefficients and corresponding entropy encoded syntax elements may form a compliant bitstream that can be used to reproduce video data at a video decoder. An entropy coding process, for example, CABAC, may include performing a binarization on syntax elements. Binarization refers to the process of converting a value of a syntax element into a series of one or more bits. These bits may be referred to as “bins.” Binarization may include one or a combination of the following coding techniques: fixed length coding, unary coding, truncated unary coding, truncated Rice coding, Golomb coding, k-th order exponential Golomb coding, and Golomb-Rice coding. For example, binarization may include representing the integer value of 5 for a syntax element as 00000101 using an 8-bit fixed length binarization technique or representing the integer value of 5 as 11110 using a unary coding binarization technique. As used herein each of the terms fixed length coding, unary coding, truncated unary coding, truncated Rice coding, Golomb coding, k-th order exponential Golomb coding, and Golomb-Rice coding may refer to general implementations of these techniques and/or more specific implementations of these coding techniques. For example, a Golomb-Rice coding implementation may be specifically defined according to a video coding standard. In the example of CABAC, for a particular bin, a context provides a most probable state (MPS) value for the bin (i.e., an MPS for a bin is one of 0 or 1) and a probability value of the bin being the MPS or the least probably state (LPS). For example, a context may indicate, that the MPS of a bin is 0 and the probability of the bin being 1 is 0.3. It should be noted that a context may be determined based on values of previously coded bins including bins in the current syntax element and previously coded syntax elements. For example, values of syntax elements associated with neighboring video blocks may be used to determine a context for a current bin.

With respect to the equations used herein, the following arithmetic operators may be used:

-   + Addition -   − Subtraction -   Multiplication, including matrix multiplication -   x^(y) Exponentiation. Specifies x to the power of y. In other     contexts, such notation is used for superscripting not intended for     interpretation as exponentiation. -   / Integer division with truncation of the result toward zero. For     example, 7/4 and −7/−4 are truncated to 1 and −7/4 and 7/−4 are     truncated to −1. -   ÷ Used to denote division in mathematical equations where no     truncation or rounding is intended.

$\frac{x}{y}$

Used to denote division in mathematical equations where no truncation or rounding is intended.

Further, the following mathematical functions may be used:

Log 2(x) the base-2 logarithm of x;

${{Min}\left( {x,y} \right)} = \left\{ {\begin{matrix} {x;} & {x<=y} \\ {y;} & {x > y} \end{matrix};{{{Max}\left( {x,y} \right)} = \left\{ \begin{matrix} {x;} & {x>=y} \\ {y;} & {x < y} \end{matrix} \right.}} \right.$

Ceil(x) the smallest integer greater than or equal to x.

With respect to the example syntax used herein, the following definitions of logical operators may be applied:

x && y Boolean logical “and” of x and y

x∥y Boolean logical “or” of x and y

! Boolean logical “not”

x ? y:z If x is TRUE or not equal to 0, evaluates to the value of y; otherwise, evaluates to the value of z.

Further, the following relational operators may be applied:

> Greater than

>= Greater than or equal to

< Less than

<= Less than or equal to

== Equal to

!= Not equal to

Further, it should be noted that in the syntax descriptors used herein, the following descriptors may be applied:

-   -   b(8): byte having any pattern of bit string (8 bits). The         parsing process for this descriptor is specified by the return         value of the function read_bits(8).     -   f(n): fixed-pattern bit string using n bits written (from left         to right) with the left bit first. The parsing process for this         descriptor is specified by the return value of the function         read_bits(n).     -   se(v): signed integer 0-th order Exp-Golomb-coded syntax element         with the left bit first.     -   tb(v): truncated binary using up to maxVal bits with maxVal         defined in the semantics of the symtax element.     -   tu(v): truncated unary using up to maxVal bits with maxVal         defined in the semantics of the symtax element.     -   u(n): unsigned integer using n bits. When n is “v” in the syntax         table, the number of bits varies in a manner dependent on the         value of other syntax elements. The parsing process for this         descriptor is specified by the return value of the function         read_bits(n) interpreted as a binary representation of an         unsigned integer with most significant bit written first.     -   ue(v): unsigned integer 0-th order Exp-Golomb-coded syntax         element with the left bit first.

As described above, video content includes video sequences comprised of a series of pictures and each picture may be divided into one or more regions. In JVET-R2001, a coded representation of a picture comprises VCL NAL units of a particular layer within an AU and contains all CTUs of the picture. For example, referring again to FIG. 2, the coded representation of Pic₃ is encapsulated in three coded slice NAL units (i.e., Slice₀ NAL unit. Slice₁ NAL unit, and Slice₂ NAL unit). It should be noted that the term video coding layer (VCL) NAL unit is used as a collective term for coded slice NAL units, i.e., VCL NAL is a collective term which includes all types of slice NAL units. As described above, and in further detail below, a NAL unit may encapsulate metadata used for decoding video data. A NAL unit encapsulating metadata used for decoding a video sequence is generally referred to as a non-VCL NAL unit. Thus, in JVET-R2001, a NAL unit may be a VCL NAL unit or a non-VCL NAL unit. It should be noted that a VCL NAL unit includes slice header data, which provides information used for decoding the particular slice. Thus, in JVET-R2001, information used for decoding video data, which may be referred to as metadata in some cases, is not limited to being included in non-VCL NAL units. JVET-R2001 provides where a picture unit (PU) is a set of NAL units that are associated with each other according to a specified classification rule, are consecutive in decoding order, and contain exactly one coded picture and where an access unit (AU) is a set of PUs that belong to different layers and contain coded pictures associated with the same time for output from the DPB. JVET-R2001 further provides where a layer is a set of VCL NAL units that all have a particular value of a layer identifier and the associated non-VCL NAL units. Further, in JVET-R2001, a PU consists of zero or one PH NAL units, one coded picture, which comprises of one or more VCL NAL units, and zero or more other non-VCL NAL units. Further, in JVET-R2001, a coded video sequence (CVS) is a sequence of AUs that consists, in decoding order, of a CVSS AU, followed by zero or more AUs that are not CVSS AUs, including all subsequent AUs up to but not including any subsequent AU that is a CVSS AU, where a coded video sequence start (CVSS) AU is an AU in which there is a PU for each layer in the CVS and the coded picture in each present picture unit is a coded layer video sequence start (CLVSS) picture. In JVET-R2001, a coded layer video sequence (CLVS) is a sequence of PUs within the same layer that consists, in decoding order, of a CLVSS PU, followed by zero or more PUs that are not CLVSS PUs, including all subsequent PUs up to but not including any subsequent PU that is a CLVSS PU. This is, in JVET-R2001, a bitstream may be described as including a sequence of AUs forming one or more CVSs.

Multi-layer video coding enables a video presentation to be decoded/displayed as a presentation corresponding to a base layer of video data and decoded/displayed one or more additional presentations corresponding to enhancement layers of video data. For example, a base layer may enable a video presentation having a basic level of quality (e.g., a High Definition rendering and/or a 30 Hz frame rate) to be presented and an enhancement layer may enable a video presentation having an enhanced level of quality (e.g., an Ultra High Definition rendering and/or a 60 Hz frame rate) to be presented. An enhancement layer may be coded by referencing a base layer. That is, for example, a picture in an enhancement layer may be coded (e.g., using inter-layer prediction techniques) by referencing one or more pictures (including scaled versions thereof) in a base layer. It should be noted that layers may also be coded independent of each other. In this case, there may not be inter-layer prediction between two layers. Each NAL unit may include an identifier indicating a layer of video data the NAL unit is associated with. As described above, a sub-bitstream extraction process may be used to only decode and display a particular region of interest of a picture. Further, a sub-bitstream extraction process may be used to only decode and display a particular layer of video. Sub-bitstream extraction may refer to a process where a device receiving a compliant or conforming bitstream forms a new compliant or conforming bitstream by discarding and/or modifying data in the received bitstream. For example, sub-bitstream extraction may be used to form a new compliant or conforming bitstream corresponding to a particular representation of video (e.g., a high quality representation).

In JVET-R2001, each of a video sequence, a GOP, a picture, a slice, and CTU may be associated with metadata that describes video coding properties and some types of metadata an encapsulated in non-VCL NAL units. JVET-R2001 defines parameters sets that may be used to describe video data and/or video coding properties. In particular. JVET-R2001 includes the following four types of parameter sets: video parameter set (VPS), sequence parameter set (SPS), picture parameter set (PPS), and adaption parameter set (APS), where a SPS applies to apply to zero or more entire CVSs, a PPS applies to zero or more entire coded pictures, a APS applies to zero or more slices, and a VPS may be optionally referenced by a SPS. A PPS applies to an individual coded picture that refers to it. In JVET-R2001, parameter sets may be encapsulated as a non-VCL NAL unit and/or may be signaled as a message. JVET-R2001 also includes a picture header (PH) which is encapsulated as a non-VCL NAL unit. In JVET-R2001, a picture header applies to all slices of a coded picture. JVET-R2001 further enables decoding capability information (DCI) and supplemental enhancement information (SEI) messages to be signaled. In JVET-R2001, DCI and SEI messages assist in processes related to decoding, display or other purposes, however, DCI and SEI messages may not be required for constructing the luma or chroma samples according to a decoding process. In JVET-R2001. DCI and SEI messages may be signaled in a bitstream using non-VCL NAL units. Further, DCI and SEI messages may be conveyed by some mechanism other than by being present in the bitstream (i.e., signaled out-of-band).

FIG. 3 illustrates an example of a bitstream including multiple CVSs, where a CVS includes AUs. and AUs include picture units. The example illustrated in FIG. 3 corresponds to an example of encapsulating the slice NAL units illustrated in the example of FIG. 2 in a bitstream. In the example illustrated in FIG. 3, the corresponding picture unit for Pic₃ includes the three VCL NAL coded slice NAL units, i.e., Slice₀ NAL unit, Slice₁ NAL unit, and Slice₂ NAL unit and two non-VCL NAL units, i.e., a PPS NAL Unit and a PH NAL unit. It should be noted that in FIG. 3. HEADER is a NAL unit header (i.e., not to be confused with a slice header). Further, it should be noted that in FIG. 3, other non-VCL NAL units, which are not illustrated may be included in the CVSs, e.g., SPS NAL units, VPS NAL units, SEI message NAL units, etc. Further, it should be noted that in other examples, a PPS NAL Unit used for decoding Pic₃ may be included elsewhere in the bitstream, e.g., in the picture unit corresponding to Pic₀ or may be provided by an external mechanism. As described in further detail below, in JVET-R2001, a PH syntax structure may be present in the slice header of a VCL NAL unit or in a PH NAL unit of the current PU.

JVET-R2001 defines NAL unit header semantics that specify the type of Raw Byte Sequence Payload (RBSP) data structure included in the NAL unit. Table 1 illustrates the syntax of the NAL unit header provided in JVET-R2001.

TABLE 1 Descriptor nal_unit_header( ) { forbidden_zero_bit f(1) nuh_reserved_zero_bit u(1) nuh_layer_id u(6) nal_unit_type u(5) nuh_temporal_id_plus1 u(3) }

JVET-R2001 provides the following definitions for the respective syntax elements illustrated in Table 1.

forbidden_zero_bit shall be equal to 0. nuh_reserved_zero_bit shall be equal to ‘0’. The value 1 of nuh_reserved_zero_bit may be specified in the future by ITU-T|ISO/IEC. Decoders shall ignore (i.e. remove from the bitstream and discard) NAL units with nuh_reserved_zero_bit equal to ‘1’. nuh_layer_id specifies the identifier of the layer to which a VCL NAL unit belongs or the identifier of a layer to which a non-VCL NAL unit applies. The value of nuh_layer_id shall be in the range of 0 to 55, inclusive. Other values for nuh_layer_id are reserved for future use by ITU-T|ISO/IEC. The value of nuh_layer_id shall be the same for all VCL NAL units of a coded picture. The value of nuh_layer_id of a coded picture or a PU is the value of the nuh_layer_id of the VCL NAL units of the coded picture or the PU. When nal_unit_type is equal to PH_NUT, EOS_NUT, or FD_NUT, nuh_layer_id shall be equal to the nuh_layer_id of associated VCL NAL unit.

NOTE—The value of nuh_layer_id of DCI, VPS, AUD, and EOB NAL units is not constrained.

nuh_temporal_id_plus1 minus1 specifies a temporal identifier for the NAL unit. The value of nuh_temporal_id_plus1 shall not be equal to 0. The variable TemporalId is derived as follows:

TemporalId=nuh_temporal_id_plus1−1

When nal_unit_type is in the range of IDR_W_RADL to RSV_IRAP_12, inclusive. TemporalId shall be equal to 0. When nal_unit_type is equal to STSA_NUT and vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] is equal to 1, TemporalId shall not be equal to 0. The value of TemporalId shall be the same for all VCL NAL units of an AU. The value of TemporalId of a coded picture, a PU, or an AU is the value of the TemporalId of the VCL NAL units of the coded picture, PU, or AU. The value of TemporalId of a sublayer representation is the greatest value of TemporalId of all VCL NAL units in the sublayer representation. The value of TemporalId for non-VCL NAL units is constrained as follows:

-   -   If nal_unit_type is equal to DCI_NUT, VPS_NUT, or SPS_NUT.         TemporalId shall be equal to 0 and the TemporalId of the AU         containing the NAL unit shall be equal to 0.     -   Otherwise, if nal_unit_type is equal to PH_NUT, TemporalId shall         be equal to the TemporalId of the PU containing the NAL unit.     -   Otherwise, if nal_unit_type is equal to EOS_NUT or EOB_NUT,         TemporalId shall be equal to 0.     -   Otherwise, if nal_unit_type is equal to AUD_NUT, FD_NUT,         PREFIX_SEI_NUT, or SUFFIX_SEI_NUT, TemporalId shall be equal to         the TemporalId of the AU containing the NAL unit.     -   Otherwise, when nal_unit_type is equal to PPS_NUT,         PREFIX_APS_NUT, or SUFFIX_APS_NUT, TemporalId shall be greater         than or equal to the TemporalId of the PU containing the NAL         unit.         NOTE—When the NAL unit is a non-VCL NAL unit, the value of         TemporalId is equal to the minimum value of the TemporalId         values of all AUs to which the non-VCL NAL unit applies. When         nal_unit_type is equal to PPS_NUT, PREFIX_APS_NUT, or         SUFFIX_APS_NUT, TemporalId may be greater than or equal to the         TemporalId of the containing AU, as all PPSs and APSs may be         included in the beginning of the bitstream (e.g., when they are         transported out-of-band, and the receiver places them at the         beginning of the bitstream), wherein the first coded picture has         TemporalId equal to 0.         nal_unit_type specifies the NAL unit type, i.e., the type of         RBSP data structure contained in the NAL unit as specified in         Table 2.         The value of nal_unit_type shall be the same for all pictures of         a CVSS AU.         NAL units that have nal_unit_type in the range of UNSPEC28 . . .         UNSPEC31, inclusive, for which semantics are not specified,         shall not affect the decoding process specified in this         Specification.         NOTE—NAL unit types in the range of UNSPEC28 . . . UNSPEC31 may         be used as determined by the application. No decoding process         for these values of nal_unit_type is specified in this         Specification. Since different applications might use these NAL         unit types for different purposes, particular care must be         exercised in the design of encoders that generate NAL units with         these nal_unit_type values, and in the design of decoders that         interpret the content of NAL units with these nal_unit_type         values. This Specification does not define any management for         these values. ‘T’hese nal_unit_type values might only be         suitable for use in contexts in which “collisions” of usage         (i.e., different definitions of the meaning of the NAL unit         content for the same nal_unit_type value) are unimportant, or         not possible, or are managed—e.g., defined or managed in the         controlling application or transport specification, or by         controlling the environment in which bitstreams are distributed.         For purposes other than determining the amount of data in the         decoding units of the bitstream, decoders shall ignore (remove         from the bitstream and discard) the contents of all NAL units         that use reserved values of nal_unit_type.         NOTE—This requirement allows future definition of compatible         extensions to this Specification.

TABLE 2 Name of NAL unit nal_unit_type nal_unit_type Content of NAL unit and RBSP syntax structure type class 0 TRAIL_NUT Coded slice of a tailing picture or subpicture* VCL slice_layer_rbsp( ) 1 STSA_NUT Coded slice, of an STSA picture or subpicture* VCL slice_layer_rbsp( ) 2 RADL_NUT Coded slice of a RADL picture or subpicture* VCL slice_layer_rbsp( ) 3 RASL_NUT Coded slice of a RASL picture or subpicture* VCL slice_layer_rbsp( ) 4 . . . 6 RSV_VCL_4 . . . Reserved non-IRAP VCL NAL unit types VCL RSV_VCL_6 7 IDR_W_RADL Coded slice of an IDR picture or subpicture* VCL 8 IDR_N_LP slice_layer_rbsp( ) 9 CRA_NUT Coded slice of a CRA picture or subpicture* VCL silce_layer_rbsp( ) 10 GDR_NUT Coded slice of a GDR picture or subpicture* VCL slice_layer_rbsp( ) 11 RSV_IRAP_11 Reserved IRAP VCL NAL unit types VCL 12 RSV_IRAP_12 13 DCI_NUT Decoding capability information non-VCL decoding_capability_information_rbsp( ) 14 VPS_NUT Video parameter set non-VCL video_parameter_set_rbsp( ) 15 SPS_NUT Sequence parameter set non-VCL seq_parameter_set_rbsp( ) 16 PPS_NUT Picture parameter set non-VCL pic_parameter_set_rbsp( ) 17 PREFIX_APS_NUT Adaptation parameter set non-VCL 18 SUFFIX_APS_NUT adaptation_parameter_set_rbsp( ) 19 PH_NUT Picture header non-VCL picture_header_rbsp( ) 20 AUD_NUT AU delimiter non-VCL access_unit_delimiter_rbsp( ) 21 EOS_MUT End of sequence non-VCL end_of_seq_rbsp( ) 22 EOB_NUT End of bitstream non-VCL end_of_bitstream_rbsp( ) 23 PREFLX_SEI_NUT Supplemental enhancement information non-VCL 24 SUFFIX_SEI_NUT sei_rbsp( ) 25 FD_NUT Filler data non-VCL filler_data_rbsp( ) 26 RSV_NVCL_26 Reserved non-VCL NAL unit types non-VCL 27 RSV_NVCL_27 28 . . . 31 UNSPEC_28 . . . Unspecified non-VCL NAL unit types non-VCL UNSPEC_31 *indicates a property of a picture when pps_mixed_nalu_types_in_pic_flag is equal to 0 and a property of the subpicture when pps_mixed_nalu_types_in_pic_flag is equal to 1. NOTE—A clean random access (CRA) picture may have associated RASL or RADL pictures present in the bitstream. NOTE—An instantaneous decoding refresh (IDR) picture having nal_unit_type equal to IDR_N_LP does not have associated leading pictures present in the bitstream. An IDR picture having nal_unit_type equal to IDR_W_RADL does not have associated RASL pictures present in the bitstream, but may have associated RADL pictures in the bitstream. The value of nal_unit_type shall be the same for all VCL NAL units of a subpicture. A subpicture is referred to as having the same NAL unit type as the VCL NAL units of the subpicture. When any two subpictures in a picture have different NAL unit types, the value of sps_subpic_treated_as_pic_flag[ ] shall be equal to 1 for all subpictures in the picture that contain at least one P or B slice. For VCL NAL units of any particular picture, the following applies:

-   -   if pps_mixed_nalu_types_in_pic_flag is equal to 0, the value of         nal_unit_type shall be the same for all VCL NAL units of a         picture, and a picture or a PU is referred to as having the same         NAL unit type as the coded slice NAL units of the picture or PU.     -   Otherwise (pps_mixed_nalu_types_in_pic_flag is equal to 1), the         following applies:         -   The picture shall have at least two subpictures.         -   VCL NAL units of the picture shall have two or more             different nal_unit_type values.         -   There shall be no VCL NAL unit of the picture that has             nal_unit_type_equal to GDR_NUT.         -   When the VCL NAL units of at least one subpicture of the             picture have a particular value of nal_unit_type equal to             IDR_W_RADL, IDR_N_LP, or CRA_NUT, the VCL NAL units of other             subpictures in the picture shall all have nal_unit_type             equal to TRAIL_NUT.             When vps_max_tid_il_ref_pics_plus1[i][j] is equal to 0 for j             equal to GeneralLayerIdx[nuh_layer_id] and any value of i in             the range of j+1 to vps_max_layers_minus1, inclusive, the             current picture shall not have both VCL NAL units with a             particular value of nal_unit_type equal to IDR_W_RADL,             IDR_N_LP, or CRA_NUT and VCL NAL units with nal_unit_type             equal to a different value than that particular value.             It is a requirement of bitstream conformance that the             following constraints apply:     -   When a picture is a leading picture of an IRAP picture, it shall         be a RADL or RASL picture.     -   When a subpicture is a leading subpicture of an IRAP subpicture,         it shall be a RADL or RASL subpicture.     -   When a picture is not a leading picture of an IRAP picture, it         shall not be a RADL or RASL picture.     -   When a subpicture is not a leading subpicture of an IRAP         subpicture, it shall not be a RADL or RASL subpicture.     -   No RASL pictures shall be present in the bitstream that are         associated with an IDR picture.     -   No RASL subpictures shall be present in the bitstream that are         associated with an IDR subpicture.     -   No RADL pictures shall be present in the bitstream that are         associated with an IDR picture having nal_unit_type equal to         IDR_N_LP.         -   NOTE—It is possible to perform random access at the position             of an IRAP PU by discarding all PUs before the IRAP PU (and             to correctly decode the IRAP picture and all the subsequent             non-RASL pictures in decoding order), provided each             parameter set is available (either in the bitstream or by             external means not specified in this Specification) when it             is referenced.     -   No RADL subpictures shall be present in the bitstream that are         associated with an IDR subpicture having nal_unit_type equal to         IDR_N_LP.     -   Any picture, with nuh_layer_id equal to a particular value         layerId, that precedes an IRAP picture with nuh_layer_id equal         to layerId in decoding order shall precede the IRAP picture in         output order and shall precede any RADL picture associated with         the IRAP picture in output order.     -   Any subpicture, with nuh_layer_id equal to a particular value         layerId and subpicture index equal to a particular value         subpicIdx, that precedes, in decoding order, an IRAP subpicture         with nuh_layer_id equal to layerId and subpicture index equal to         subpicIdx shall precede, in output order, the IRAP subpicture         and all its associated RADL subpictures.     -   Any picture, with nuh_layer_id equal to a particular value         layerId, that precedes a recovery point picture with         nuh_layer_id equal to layerId in decoding order shall precede         the recovery point picture in output order.     -   Any subpicture, with nuh_layer_id equal to a particular value         layerId and subpicture index equal to a particular value         subpicIdx, that precedes, in decoding order, a subpicture with         nuh_layer_id equal to layerId and subpicture index equal to         subpicIdx in a recovery point picture shall precede that         subpicture in the recovery point picture in output order.     -   Any RASL picture associated with a CRA picture shall precede any         RADL picture associated with the CRA picture in output order.     -   Any RASL subpicture associated with a CRA subpicture shall         precede any RADL subpicture associated with the CRA subpicture         in output order.     -   Any RASL picture, with nuh_layer_id equal to a particular value         layerId, associated with a CRA picture shall follow, in output         order, any IRAP or GDR picture with nuh_layer_id equal to         layerId that precedes the CRA picture in decoding order.     -   Any RASL subpicture, with nuh_layer_id equal to a particular         value layerId and subpicture index equal to a particular value         subpicIdx, associated with a CRA subpicture shall follow, in         output order, any IRAP or GDR subpicture, with nuh_layer_id         equal to layerId and subpicture index equal to subpicIdx, that         precedes the CRA subpicture in decoding order.     -   If sps_field_seq_flag is equal to 0 and the current picture,         with nuh_layer_id equal to a particular value layerId, is a         leading picture associated with an IRAP picture, it shall         precede, in decoding order, all non-leading pictures that are         associated with the same IRAP picture. Otherwise, let picA and         picB be the first and the last leading pictures, in decoding         order, associated with an IRAP picture, respectively, there         shall be at most one non-leading picture with nuh_layer_id equal         to layerId preceding picA in decoding order, and there shall be         no non-leading picture with nuh_layer_id equal to layerId         between picA and picB in decoding order.     -   If sps_field_seq_flag is equal to 0 and the current subpicture,         with nuh_layer_id equal to a particular value layerId and         subpicture index equal to a particular value subpicIdx, is a         leading subpicture associated with an IRAP subpicture, it shall         precede, in decoding order, all non-leading subpictures that are         associated with the same IRAP subpicture. Otherwise, let subpicA         and subpicB be the first and the last leading subpictures, in         decoding order, associated with an IRAP subpicture,         respectively, there shall be at most one non-leading subpicture         with nuh_layer_id equal to layerId and subpicture index equal to         subpicIdx preceding subpicA in decoding order, and there shall         be no non-leading picture with nuh_layer_id equal to layerId and         subpicture index equal to subpicIdx between picA and picB in         decoding order.

It should be noted that generally, an Intra Random Access Point (IRAP) picture is a picture that does not refer to any pictures other than itself for prediction in its decoding process. In JVET-R2001, an IRAP picture may be a clean random access (CRA) picture or an instantaneous decoder refresh (IDR) picture. In JVET-R2001, the first picture in the bitstream in decoding order must be an IRAP or a gradual decoding refresh (GDR) picture. JVET-R2001 describes the concept of a leading picture, which is a picture that precedes the associated IRAP picture in output order. JVET-R2001 further describes the concept of a trailing picture which is a non-IRAP picture that follows the associated IRAP picture in output order. Trailing pictures associated with an IRAP picture also follow the IRAP picture in decoding order. For IDR pictures, there are no trailing pictures that require reference to a picture decoded prior to the IDR picture. JVET-R2001 provides where a CRA picture may have leading pictures that follow the CRA picture in decoding order and contain inter picture prediction references to pictures decoded prior to the CRA picture. Thus, when the CRA picture is used as a random access point these leading pictures may not be decodable and are identified as random access skipped leading (RASL) pictures. The other type of picture that can follow an IRAP picture in decoding order and precede it in output order is the random access decodable leading (RADL) picture, which cannot contain references to any pictures that precede the IRAP picture in decoding order. A GDR picture, is a picture for which each VCL NAL unit has nal_unit_type equal to GDR_NUT. If the current picture is a GDR picture that is associated with a picture header which signals a syntax element recovery_poc_cnt and there is a picture picA that follows the current GDR picture in decoding order in the CLVS and that has PicOrderCntVal equal to the PicOrderCntVal of the current GDR picture plus the value of recovery_poc_cnt, the picture picA is referred to as the recovery point picture.

As provided in Table 2, a NAL unit may include a video parameter set (VPS) syntax structure. Table 3 illustrates the syntax structure of the video parameter set provided in JVET-R2001.

TABLE 3 Descriptor video_parameter_set_rbsp( ) { vps_video_parameter_set_id  u(4) vps_max_layers_minus1  u(6) vps_max_sublayers_minus1  u(3) if( vps_max_layers_minus1 > 0 && vps_max_sublayers_minus1 > 0 ) vps_all_layers_same_num_sublayers_flag  u(1) if( vps_max_layers_minus1 > 0 ) vps_all_independent_layers_flag  u(1) for( i = 0; i <= vps_max_layers_minus1; i++ ) { vps_layer_id[ i ]  u(6) if( i > 0 && !vps_all_independent_layers_flag ) { vps_independent_layer_flag[ i ]  u(1) if( !vps_independent_layer_flag[ i ] ) { vps_max_tid_ref_present_flag[ i ]  u(1) for( j = 0; j < i; j++ ) { vps_direct_ref_layer_flag[ i ][ j ]  u(1) if( vps_max_tid_ref_present_flag[ i ] && vps_direct_ref_layer_flag[ i ][ j ] ) vps_max_tid_il_ref_pics_plusl[ i ][ j ]  u(3) } } } } if( vps_max_layers_minus1 > 0 ) { if( vps_all_independent_layers_flag ) vps_each_layer_is_an_ols_flag  u(1) if( !vps_each_layer_is_an_ols_flag ) { if( !vps_all_independent_layers_flag ) vps_ols_mode_idc  u(2) if( vps_ols_mode_idc = = 2 ) { vps_num_output_layer_sets_minus1  u(8) for( i = 1; i <= vps_num_output_layer_sets_minus1; i ++) for) j = 0; j <= vps_max_layers_minus1; j++ ) vps_ols_output_layer_flag[ i ][ j ]  u(1) } } } vps_num_ptls_minus1  u(8) for( i =0; i <= vps_num_ptls_minus1; i++ ) { if( i > 0 ) vps_pt_present_flag[ i ]  u(1) if( !vps_all_layers_same_num_sublayers_flag ) vps_ptl_max_temporal_id[ i ]  u(3) } while( !byte_aligned( ) ) vps_ptl_alignment_zero_bit /* equal to 0 */  f(1) for( i = 0; i <= vps_num_ptls_minus1; i++ ) profile_tier_level( vps_pt_present_flag[ i ], vps_ptl_max_temporal_id[ i ] ) for( i = 0; i < TotalNumOlss; i++ ) if( vps_num ptls_minus1 > 0 && vps_num_ptls_minus1 + 1 != TotalNumOlss ) vps_ols_ptl_idx[ i ]  u(8) if( !vps_each_layer_is_an_ols_flag ) { vps_num_dpb_params_minus1 ue(v) if( vps_max_sublayers_minus1 > 0 ) vps_sublayer_dpb_params_present_flag  u(1) for( i = 0; i < VpsNumDpbParams; i++ ) { if( !vps_all_layers_same_num_sublayers_flag ) vps_dpb_max_temporal_id[ i ]  u(3) dpb_parameters( vps_dpb_max_temporal_id[ i ], vps_sublayer_dpb_params_present_flag ) } for( i = 0; i < NumMultiLayerOlss; i++ ) { vps_ols_dpb_pic_width[ i ] ue(v) vps_ols_dpb_pic_height[ i ] ue(v) vps_ols_dpb_chroma_format[ i ]  u(2) vps_ols_dpb_bitdepth_minus8[ i ] ue(v) if( VpsNumDpbParams > 1 && vps_num_dpb_params != NumMultiLayerOlss ) vps_ols_dpb_params_idx[ i ] ue(v) } vps_general_hrd_params_present_flag  u(1) } if( vps_general_hrd_params_present_flag ) { general_hrd_parameters( ) if( vps_max_sublayers_minus1 > 0 ) vps_sublayer_cpb_params_present_flag  u(1) vps_num_ols_hrd_params_minus1 ue(v) for( i = 0; i <= vps_num_ols_hrd_params_minus1; i++ ) { if( !vps_all_layers_same_num_sublayers_flag ) hrd_max_tid[ i ]  u(3) firstSubLayer = vps_sublayer_cpb_params_present_flag ? 0 : vps_hrd_max_tid[ i ] ols_hrd_parameters( firstSubLayer, vps_hrd_max_tid[ i ] ) } if( vps_num_ols_hrd_params_minus1 > 0 && vps_num_ols_hrd_params_minus1 + 1 != NumMultiLayerOlss ) for( i = 0; i < NumMultiLayerOlss; i++ ) vps_ols_hrd_idx[ i ] ue(v) } vps_extension_flag  u(1) if( vps_extension_flag ) while( more_rbsp_data( ) ) vps_extension_data_flag  u(1) rbsp_trailing_bits( ) }

With respect to Table 3, JVET-R2001 provides the following semantics:

A VPS RBSP shall be available to the decoding process prior to it being referenced, included in at least one AU with TemporalId equal to 0 or provided through external means. All VPS NAL units with a particular value of vps_video_parameter_set_id in a CVS shall have the same content. vps_video_parameter_set_id provides an identifier for the VPS for reference by other syntax elements. The value of vps_video_parameter_set_id shall be greater than 0. vps_max_layers_minus1 plus 1 specifies the maximum allowed number of layers in each CVS referring to the VPS. vps_max_sublayers_minus1 plus 1 specifies the maximum number of temporal sublayers that may be present in a layer in each CVS referring to the VPS. The value of vps_max_sublayers_minus1 shall be in the range of 0 to 6, inclusive. vps_all_layers_same_num_sublayers_flag equal to 1 specifies that the number of temporal sublayers is the same for all the layers in each CVS referring to the VPS. vps_all_layers_same_num_sublayers_flag equal to 0 specifies that the layers in each CVS referring to the VPS may or may not have the same number of temporal sublayers. When not present, the value of vps_all_layers_same_num_sublayers_flag is inferred to be equal to 1. vps_all_independent_layers_flag equal to 1 specifies that all layers in the CVS are independently coded without using inter-layer prediction. vps_all_independent_layers_flag equal to 0 specifies that one or more of the layers in the CVS may use inter-layer prediction. When not present, the value of vps_all_independent_layers_flag is inferred to be equal to 1. vps_layer_id[i] specifies the nuh_layer_id value of the i-th layer. For any two non-negative integer values of m and n, when m is less than n, the value of vps_layer_id[m] shall be less than vps_layer_id[n]. vps_independent_layer_flag[i] equal to 1 specifies that the layer with index i does not use inter-layer prediction. vps_independent_layer_flag[i] equal to 0 specifies that the layer with index i may use inter-layer prediction and the syntax elements vps_direct_ref_layer_flag[i][j] for j in the range of 0 to i−1, inclusive, are present in VPS. When not present, the value of vps_independent_layer_flag[i] is inferred to be equal to 1. vps_max_tid_ref_present_flag[i] equal to 1 specifies that the syntax element vps_max_tid_il_ref_pics_plus1[i][j] is present. vps_max_tid_refpresent_flag[i] equal to 0 specifies that the syntax element vps_max_tid_il_ref_pics_plus1[i][j] is not present. vps_direct_ref_layer_flag[i][j] equal to 0 specifies that the layer with index j is not a direct reference layer for the layer with index i. vps_direct_ref_layer_flag [i][j] equal to 1 specifies that the layer with index j is a direct reference layer for the layer with index i. When vps_direct_ref_layer_flag[i][j] is not present for i and j in the range of 0 to vps_max_layers_minus1, inclusive, it is inferred to be equal to 0. When vps_independent_layer_flag[i] is equal to 0, there shall be at least one value of j in the range of 0 to i−1, inclusive, such that the value of vps_direct_ref_layer_flag[i][j] is equal to 1. The variables NumDirectRefLayers[i], DirectRefLayerIdx[i][d], NumRefLayers[i], RefLayerIdx[i][r], and LayerUsedAsRefLayerFlag[j] are derived as follows:

for( i = 0; i <= vps_max_layers_minus1; i++ ) { for( j = 0; j <= vps_max_layers_minus1; j++ ) { dependencyFlag[ i ][ j ] = vps_direct_ref_layer_flag[ i ][ j ] for( k = 0; k < i; k++ ) if( vps_direct_ref_layer_flag[ i ][ k ] && dependencyFlag[ k ][ j ] ) dependencyFlag[ i ][ j ] = 1 } LayerUsedAsRefLayerFlag[ i ] = 0 } for( i = 0; i <= vps_max_layers_minus1; i++ ) { for(j = 0, d = 0, r = 0; j <= vps_max_layers_minus1; j++ ) { if( vps_direct_ref_layer_flag[ i ][ j ] ) { DirectRefLayerIdx[ i ][ d++ ] = j LayerUsedAsRefLayerFlag[ j ] = 1 } if( dependencyFlag[ i ][ j ] ) RefLayerIdx[ i ][ r++ ] = j } NumDirectRefLayers[ i ] = d NumRefLayers[ i ] = r } The variable GeneralLayerIdx[i], specifying the layer index of the layer with nuh_layer_id equal to vps_layer_id[i], is derived as follows:

for(i = 0; i <= vps_max_layers_minus1; i++ ) GeneralLayerIdx[ vps_layer_id[ i ] ] = i For any two different values of i and j, both in the range of 0 to vps_max_layers_minus1, inclusive, when dependencyFlag[i][j] equal to 1, it is a requirement of bitstream conformance that the values of sps_chroma_format_idc and sps_bit_depth_minus8 that apply to the i-th layer shall be equal to the values of sps_chroma_format_idc and sps_bit_depth_minus8, respectively, that apply to the j-th layer. vps_max_tid_il_ref_pics_plus1[i][j] equal to 0 specifies that the pictures of the j-th layer that are neither IRAP pictures nor GDR pictures with ph_recovery_poc_cnt equal to 0 are not used as ILRPs for decoding of pictures of the i-th layer. vps_max_tid_il_ref_pics_plus1[i][j] greater than 0 specifies that, for decoding pictures of the i-th layer, no picture from the j-th layer with TemporalId greater than vps_max_tid_il_ref_pics_plus1[i][j]−1 is used as ILRP. When not present, the value of vps_max_tid_il_ref_pics_plus1[i][j] is inferred to be equal to vps_max_sublayers_minus1+1. vps_each_layer_is_an_ols_flag equal to 1 specifies that each OLS contains only one layer and each layer itself in a CVS referring to the VPS is an OLS with the single included layer being the only output layer. vps_each_layer_is_an_ols_flag equal to 0 that at least one OLS contains more than one layer. If vps_max_layers_minus1 is equal to 0, the value of vps_each_layer_is_an_ols_flag is inferred to be equal to 1. Otherwise, when vps_all_independent_layers_flag is equal to 0, the value of vps_each_layer_is_an_ols_flag is inferred to be equal to 0. vps_ols_mode_idc equal to 0 specifies that the total number of OLSs specified by the VPS is equal to vps_max_layers_minus1+1, the i-th OLS includes the layers with layer indices from 0 to i, inclusive, and for each OLS only the highest layer in the OLS is an output layer. vps_ols_mode_idc equal to 1 specifies that the total number of OLSs specified by the VPS is equal to vps_max_layers_minus1+1, the i-th OLS includes the layers with layer indices from 0 to i, inclusive, and for each OLS all layers in the OLS are output layers. vps_ols_mode_idc equal to 2 specifies that the total number of OLSs specified by the VPS is explicitly signalled and for each OLS the output layers are explicitly signalled and other layers are the layers that are direct or indirect reference layers of the output layers of the OLS. The value of vps_ols_mode_idc shall be in the range of 0 to 2, inclusive. The value 3 of vps_ols_mode_idc is reserved for future use by ITU-T|ISO/IEC. When vps_all_independent_layers_flag is equal to 1 and vps_each_layer_is_an_ols_flag is equal to 0, the value of vps_ols_mode_idc is inferred to be equal to 2. vps_num_output_layer_sets_minus1 plus 1 specifies the total number of OLSs specified by the VPS when vps_ols_mode_idc is equal to 2. The variable TotalNumOlss, specifying the total number of OLSs specified by the VPS, is derived as follows:

if( vps_max_layers_minus1 = = 0 ) TotalNumOlss = 1 else if( vps_each_layer_is_an_ols_flag | | vps_ols_mode_idc = = 0 | | vps_ols_mode_idc = = 1 ) TotalNumOlss = vps_max_layers_minus1 + 1 else if( vps_ols_mode_idc = = 2 ) TotalNumOlss = vps_num_output_layer_sets_minus1 + 1 vps_ols_output_layer_flag[i][j] equal to 1 specifies that the layer with nuh_layer_id equal to vps_layer_id[j] is an output layer of the i-th OLS when vps_ols_mode_idc is equal to 2. vps_ols_output_layer_flag[i][j] equal to 0 specifies that the layer with nuh_layer_id equal to vps_layer_id[j] is not an output layer of the i-th OLS when vps_ols_mode_idc is equal to 2. The variable NumOutputLayersInOls[i], specifying the number of output layers in the i-th OLS, the variable NumSubLayersInLayerinOLS[i][j], specifying the number of sublayers in the j-th layer in the i-th OLS, the variable OutputLayerIdInOls[i][j], specifying the nuh_layer_id value of the j-th output layer in the i-th OLS, and the variable LayerUsedAsOutputLayerFlag[k], specifying whether the k-tb layer is used as an output layer in at least one OLS, are derived as follows:

NumOutputLayersInOls[ 0 ] = 1 OutputLayerIdInOls[ 0 ][ 0 ] = vps_layer_id[ 0 ] NumSubLayersInLayerInOLS[ 0 ][ 0 ] = vps_max_sub_layers_minus1 + 1 LayerUsedAsOutputLayerFlag[ 0 ] = 1 for( i = 1, i <= vps_max_layers_minus1; i++ ) { if( vps_each_layer_is_an_ols_flag | | vps_ols_mode_idc < 2 ) LayerUsedAsOutputLayerFlag[ i ] = 1 else /*( !vps_each_layer_is_an_ols_flag && vps_ols_mode_idc = = 2 ) */ LayerUsedAsOutputLayerFlag[ i ] = 0 } for( i = 1; i < TotalNumOlss; i++ ) if( vps_each_layer_is_an_ols_flag | | vps_ols_mode_idc = = 0 ) { NumOutputLayersInOls[ i ] = 1 OutputLayerIdInOls[ i ][ 0 ] = vps_layer_id[ i ] if( vps_each_layer_is_an_ols_flag ) NumSubLayersInLayerInOLS[ i ][ 0 ] = vps_max_sub_layers_minus1 + 1 else { NumSubLayersInLayerInOLS[ i ][ i ] = vps_max_sub_layers_minus1 + 1 for( k = i − 1, k >= 0; k− − ) { NumSubLayersInLayerInOLS[ i ][ k ] = 0 for( m = k + 1; m <= i; m++ ) { maxSublayerNeeded = min( NumSubLayersInLayerInOLS[ i ][ m ], vps_max_tid_il_ref_pics_plus1[ m ][ k ] ) if( vps_direct_ref_layer_flag[ m ][ k ] && NumSubLayersInLayerInOLS[ i ][ k ] < maxSublayerNeeded ) NumSubLayersInLayerInOLS[ i ][ k ] = maxSublayerNeeded } } } } else if( vps_ols_mode_idc = = 1 ) { NumOutputLayersInOls[ i ] = i + 1 for( j = 0; j < NumOutputLayersInOls[ i ]; j++ ) { OutputLayerIdInOls[ i ][ j ] = vps_layer_id[ j ] NumSubLayersInLayerInOLS[ i ][ j ] = vps_max_sub_layers_minus1 + 1 } } else if( vps_ols_mode_idc = = 2 ) { for( j = 0; j <= vps_max_layers_minus1; j++ ) { layerIncludedInOlsFlag[ i ][ j ] = 0 NumSubLayersInLayerInOLS[ i ][ j ] = 0 } highestIncludedLayer = 0 numLayerInOls = 0 for( k = 0, j = 0; k <= vps_max_layers_minus1; k++ ) if( vps_ols_output_layer_flag[ i ][ k ] ) { layerIncludedInOlsFlag[ i ][ k ] = 1 highestIncludedLayer = k numLayerInOls++ LayerUsedAsOutputLayerFlag[ k ] = 1 OutputLayerIdx[ i ][ j ] = k OutputLayerIdInOls[ i ][ j++ ] = vps_layer_id[ k ] NumSubLayersInLayerInOLS[ i ][ k ] = vps_max_sub_layers_minus1 + 1 } NumOutputLayersInOls[ i ] = j for( j = 0; j < NumOutputLayersInOls[ i ]; j++ ) { idx = OutputLayerIdx[ i ][ j ] for( k = 0; k < NumRefLayers[ idx ]; k++ ) { if (!layerIncludedInOlsFlag[ i ][ RefLayerIdx[ idx ][ k ] ] ) numLayerInOls++ layerIncludedInOlsFlag[ i ][ RefLayerIdx[ idx ][ k ] ] = 1 } } for( k = highestIncludedLayer − 1; k >= 0; k− − ) if( layerIncludedInOlsFlag[ i ][ k ] && !vps_ols_output_layer_flag[ i ][ k ] ) for( m = k + 1; m <= highestIncludedLayer; m++ ) { maxSublayerNeeded = min( NumSubLayersInLayerInOLS[ i ][ m ], vps_max_tid_il_ref_pics_plus1[ m ][ m ][ k ] ) if( vps_direct_ref_layer_flag[ m ][ k ] && layerIncludedInOlsFlag[ i ][ m ] && NumSubLayersInLayerInOLS[ i ][ k ] < maxSublayerNeeded ) NumSubLayersInLayerInOLS[ i ][ k ] = maxSublayerNeeded } } For each value of i in the range of 0 to vps_max_layers_minus1, inclusive, the values of LayerUsedAsRefLayerFlag[i] and LayerUsedAsOutputLayerFlag[i] shall not be both equal to 0. In other words, there shall be no layer that is neither an output layer of at least one OLS nor a direct reference layer of any other layer. For each OLS, there shall be at least one layer that is an output layer. In other words, for any value of i in the range of 0 to TotalNumOlss−1, inclusive, the value of NumOutputLayersInOls[i] shall be greater than or equal to 1. The variable NumLayersInOls[i], specifying the number of layers in the i-th OLS, the variable LayerIdInOls[i][j], specifying the nuh_layer_id value of the j-th layer in the i-th OLS, and the variable NumMultiLayerOlss, specifying the number of multi-layer OLSs (i.e., OLSs that contain more than one layer), are derived as follows:

NumLayersInOls[ 0 ] = 1 LayerIdInOls[ 0 ][ 0 ] = vps_layer_id[ 0 ] NumMultiLayerOlss = 0 for( i = 1; i < TotalNumOlss; i++ ) { if( vps_each_layer_is_an_ols_flag ) { NumLayersInOls[ i ] = 1 LayerIdInOls[ i ][ 0 ] = vps_layer_id[ i ] } else if( vps_ols_mode_idc = = 0 | | vps_ols_mode_idc = = 1 ) { NumLayersInOls[ i ] = i + 1 for( j = 0; j < NumLayersInOls[ i ]; j++ ) LayerIdInOls[ i ][ j ] = vps_layer_id[ j ] } else if( vps_ols_mode_idc = = 2 ) { for( k = 0, j = 0; k <= vps_max_layers_minus1; k++ ) if( layerIncludedInOlsFlag[ i ][ k ] ) LayerIdInOls[ i ][ j++ ] = vps_layer_id[ k ] NumLayersInOls[ i ] = j } if( NumLayersInOls[ i ] > 1 ) { MultiLayerOlsIdx[ i ] = NumMultiLayerOlss NumMultiLayerOlss++ } } NOTE - The 0-th OLS contains only the lowest layer (i.e., the layer with nuh_layer_id equal to vps_layer_id[ 0 ]) and for the 0-th OLS the only included layer is output. The variable OlsLayerIdx[i][j], specifying the OLS layer index of the layer with nuh_layer_id equal to LayerIdInOls[i][j], is derived as follows:

for( i = 0; i < TotalNumOlss; i++ ) for j = 0; j < NumLayersInOls[ i ]; j++ ) OlsLayerIdx[ i ][ LayerIdInOls[ i ][ j ] ] = j The lowest layer in each OLS shall be an independent layer. In other words, for each i in the range of 0 to TotalNumOlss−1, inclusive, the value of vps_independent_layer_flag[GeneralLayerIdx[LayerIdInOls[i][0]]] shall be equal to 1.

Each layer shall be included in at least one OLS specified by the VPS. In other words, for each layer with a particular value of nuh_layer_id nuhLayerId equal to one of vps_layer_id[k] for k in the range of 0 to vps_max_layers_minus1, inclusive, there shall be at least one pair of values of i and j, where i is in the range of 0 to TotalNumOlss−1, inclusive, and j is in the range of NumLayersInOls[i]−1, inclusive, such that the value of LayerIdInOls[i][j] is equal to nuhLayerId.

vps_num_ptls_minus1 plus 1 specifies the number of profile_tier_level( ) syntax structures in the VPS. The value of vps_num_ptls_minus1 shall be less than TotalNumOlss. vps_pt_present_flag[i] equal to 1 specifies that profile, tier, and general constraints information are present in the i-th profile_tier_level( ) syntax structure in the VPS. vps_pt_present_flag[i] equal to 0 specifies that profile, tier, and general constraints information are not present in the i-th profile_tier_level( ) syntax structure in the VPS. The value of vps_pt_present_flag[0] is inferred to be equal to 1. When vps_pt_present_flag[i] is equal to 0, the profile, tier, and general constraints information for the i-th profile_tier_level( ) syntax structure in the VPS are inferred to be the same as that for the (i−1)-th profile_tier_level( ) syntax structure in the VPS. vps_ptl_max_temporal_id[i] specifies the TemporalId of the highest sublayer representation for which the level information is present in the i-th profile_tier_level( ) syntax structure in the VPS. The value of vps_ptl_max_temporal_id[i] shall be in the range of 0 to vps_max_sublayers_minus1, inclusive. When not present, the value of vps_ptl_max_temporal_id[i] is inferred to be equal to vps_max_sublayers_minus1. vps_ptl_alignment_zero_bit shall be equal to 0. vps_ols_pt_idx[i] specifies the index, to the list of profile_tier_level( ) syntax structures in the VPS, of the profile_tier_level( ) syntax structure that applies to the i-th OLS. When present, the value of vps_ols_ptl_idx[i] shall be in the range of 0 to vps_num_ptls_minus1, inclusive.

When not present, the value of vps_ols_ptl_idx[i] is inferred as follows:

-   -   If vps_num_ptls_minus1 is equal to 0, the value of         vps_ols_ptl_idx[i] is inferred to be equal to 0.     -   Otherwise (vps_num_ptls_minus1 is greater than 0 and         vps_num_ptls_minus1+1 is equal to TotalNumOlss), the value of         vps_ols_ptl_idx[i] is inferred to be equal to i.         When NumLayersInOls[i] is equal to 1, the profile_tier_level( )         syntax structure that applies to the i-th OLS is also present in         the SPS referred to by the layer in the i-th OLS. It is a         requirement of bitstream conformance that, when         NumLayersInOls[i] is equal to 1, the profile_tier_level( )         syntax structures signalled in the VPS and in the SPS for the         i-th OLS shall be identical.         Each profile_tier_level( ) syntax structure in the VPS shall be         referred to by at least one value of vps_ols_ptl_idx[i] for i in         the range of 0 to TotalNumOlss−1, inclusive.         vps_num_dpb_params_minus1 plus 1, when present, specifies the         number of dpb_parameters( ) syntax structures in the VPS. The         value of vps_num_dpb_params_minus1 shall be in the range of 0 to         NumMultiLayerOlss−1, inclusive. The variable VpsNumDpbParams,         specifying the number of dpb_parameters( ) syntax structures in         the VPS, is derived as follows:

if( vps_each_layer_is_an_ols_flag ) VpsNumDpbParams = 0 else VpsNumDpbParams = vps_num_dpb_params_minus1 + 1 vps_sublayer_dpb_params_present_flag is used to control the presence of max_dec_pic_buffering_minus1[ ], max_num_reorder_pics[ ], and max_latency_increase_plus1[ ] syntax elements in the dpb_parameters( ) syntax structures in the VPS. When not present, vps_sub_dpb_params_info_present_flag is inferred to be equal to 0. vps_dpb_max_temporal_id[i] specifies the TemporalId of the highest sublayer representation for which the DPB parameters may be present in the i-th dpb_parameters( ) syntax structure in the VPS. The value of vps_dpb_max_temporal_id[i] shall be in the range of 0 to vps_max_sublayers_minus1, inclusive. When not present, the value of vps_dpb_max_temporal_id[i] is inferred to be equal to vps_max_sublayers_minus1. vps_ols_dpb_pic_width[i] specifies the width, in units of luma samples, of each picture storage buffer for the i-th multi-layer OLS. vps_ols_dpb_pic_height[i] specifies the height, in units of luma samples, of each picture storage buffer for the i-th multi-layer OLS. vps_ols_dpb_chroma_format[i] specifies the greatest allowed value of sps_chroma_format_idc for all SPSs that are referred to by CLVSs in the CVS for the i-th multi-layer OLS. vps_ols_dpb_bitdepth_minus8[i] specifies the greatest allowed value of sps_bit_depth_minus8 for all SPSs that are referred to by CLVSs in the CVS for the i-th multi-layer OLS.

-   -   NOTE—For decoding an OLS containing more than one layer and         having OLS index i, the decoder can safely allocate memory for         the DPB according to the values of the syntax elements         vps_ols_dpb_pic_width[i], vps_ols_dpb_pic_height[i],         vps_ols_dpb_chroma_format[i], and         vps_ols_dpb_bitdepth_minus8[i].         vps_ols_dpb_params_idx[i] specifies the index, to the list of         dpb_parameters( ) syntax structures in the VPS, of the         dpb_parameters( ) syntax structure that applies to the i-th         multi-layer OLS. When present, the value of         vps_ols_dpb_params_idx[i] shall be in the range of 0 to         VpsNumDpbParams−1, inclusive.         When vps_ols_dpb_params_idx[i] is not present, it is inferred as         follows:     -   If VpsNumDpbParams is equal to 1, the value of         vps_ols_dpb_params_idx[i] to be equal to 0.     -   Otherwise (VpsNumDpbParams is greater than 1 and equal to         NumMultiLayerOlss), the value of vps_ols_dpb_params_idx[i] is         inferred to be equal to i.         For a single-layer OLS, the applicable dpb_parameters( ) syntax         structure is present in the SPS referred to by the layer in the         OLS.         Each dpb_parameters( ) syntax structure in the VPS shall be         referred to by at least one value of vps_ols_dpb_params_idx[i]         for i in the range of 0 to NumMultiLayerOlss−1, inclusive.         vps_general_hrd_params_present_flag equal to 1 specifies that         the VPS contains a general_hrd_parameters( ) syntax structure         and other HRD parameters. vps_general_hrd_params_present_flag         equal to 0 specifies that the VPS does not contain a         general_hrd_parameters( ) syntax structure or other HRD         parameters. When not present, the value of         vps_general_hrd_params_present_flag is inferred to be equal to         0.         When NumLayersInOls[i] is equal to 1, the         general_hrd_parameters( ) syntax structure and the         ols_hrd_parameters( ) syntax structure that apply to the i-th         OLS are present in the SPS referred to by the layer in the i-th         OLS.         vps_sublayer_cpb_params_present_flag equal to 1 specifies that         the i-th ols_hrd_parameters( ) syntax structure in the VPS         contains HRD parameters for the sublayer representations with         TemporalId in the range of 0 to vps_hrd_max_tid[i], inclusive.         vps_sublayer_cpb_params_present_flag equal to 0 specifies that         the i-th ols_hrd_parameters( ) syntax structure in the VPS         contains HRD parameters for the sublayer representation with         TemporalId equal to vps_hrd_max_tid[i] only. When         vps_max_sublayers_minus1 is equal to 0, the value of         vps_sublayer_cpb_params_present_flag is inferred to be equal to         0.

When vps_sublayer_cpb_params_present_flag is equal to 0, the HRD parameters for the sublayer representations with TemporalId in the range of 0 to vps_hrd_max_tid[i]−1, inclusive, are inferred to be the same as that for the sublayer representation with TemporalId equal to vps_hrd_max_tid[i]. These include the HRD parameters starting from the fixed_pic_rate_general_flag[i] syntax element till the sublayer_hrd_parameters(i) syntax structure immediately under the condition “if(general_vcl_hrd_params_present_flag)” in the ols_hrd_parameters syntax structure.

vps_num_ols_hrd_params_minus1 plus 1 specifies the number of ols_hrd_parameters( ) syntax structures present in the VPS when vps_general_hrd_params_present_flag is equal to 1. The value of vps_num_ols_hrd_params_minus1 shall be in the range of 0 to NumMultiLayerOlss−1, inclusive. vps_hrd_max_tld[i] specifies the TemporalId of the highest sublayer representation for which the HRD parameters are contained in the i-th ols_hrd_parameters( ) syntax structure. The value of vps_hrd_max_tid[i] shall be in the range of 0 to vps_max_sublayers_minus1, inclusive. When not present, the value of vps_hrd_max_tid[i] is inferred to be equal to vps_max_sublayers_minus1. vps_ols_hrd_idx[i] specifies the index, to the list of ols_hrd_parameters( ) syntax structures in the VPS, of the ols_hrd_parameters( ) syntax structure that applies to the i-th multi-layer OLS. The value of vps_ols_hrd_idx[i] shall be in the range of 0 to vps_num_ols_hrd_params_minus1, inclusive. When NumLayersInOls[i] is greater than 1 and vps_ols_hrd_idx[i] is not present, it is inferred as follows:

-   -   If vps_num_ols_hrd_params_minus1 is equal to 0, the value of         vps_ols_hrd_idx[[i] is inferred to be equal to 0.     -   Otherwise (vps_num_ols_hrd_params_minus1 is greater than 0 and         vps_num_ols_hrd_params_minus1+1 is equal to NumMultiLayerOlss),         the value of vps_ols_hrd_idx[i] is inferred to be equal to i.         For a single-layer OLS, the applicable ols_hrd_parameters( )         syntax structure is present in the SPS referred to by the layer         in the OLS.         Each ols_hrd_parameters( ) syntax structure in the VPS shall be         referred to by at least one value of vps_ols_hrd_idx[i] for i in         the range of 1 to NumMultiLayerOlss−1, inclusive.         vps_extension_flag equal to 0 specifies that no         vps_extension_data_flag syntax elements are present in the VPS         RBSP syntax structure. vps_extension_flag equal to 1 specifies         that there are vps_extension_data_flag syntax elements present         in the VPS RBSP syntax structure.         vps_extension_data_flag may have any value. Its presence and         value do not affect decoder conformance to profiles specified in         this version of this Specification. Decoders conforming to this         version of this Specification shall ignore all         vps_extension_data_flag syntax elements.

As provided in Table 3, a VPS may include the profile_tier_level( ) syntax structure. Table 4 illustrates the profile_tier_level( ) syntax structure provided in JVET-R2001.

TABLE 4 Descriptor profile_tier_level( profileTierPresentFlag, maxNumSubLayersMinus1 ) { if( profileTierPresentFlag ) { general_profile_idc  u(7) general_tier_flag  u(1) general_constraint_info( ) } general_level_idc  u(8) if( profileTierPresentFlag ) { num_sub_profiles  u(8) for( i = 0; i < num_sub_profiles; i++ ) general_sub_profile_idc[ i ] u(32) } for( i = 0; i < maxNumSubLayersMinus1; i++ ) sublayer_level_present_flag[ i ]  u(1) while( !byte_aligned( ) ) ptl_alignment_zero_bit  f(1) for( i = 0; i < maxNumSubLayersMinus1; i++ ) if( sublayer_level_present_flag[ i ] ) sublayer_level_idc[ i ]  u(8) }

With respect to Table 4, JVET-R2001 provides the following semantics:

A profile_tier_level( ) syntax structure provides level information and, optionally, profile, tier, sub-profile, and general constraints information. When the profile_tier_level( ) syntax structure is included in a VPS, the OlsInScope is one or more OLSs specified by the VPS. When the profile_tier_level( ) syntax structure is included in an SPS, the OlsInScope is the OLS that includes only the layer that is the lowest layer among the layers that refer to the SPS, and this lowest layer is an independent layer. general_profile_idc indicates a profile to which OlsInScope conforms as specified. Bitstreams shall not contain values of general_profile_idc other than those specified. Other values of general_profile_idc are reserved for future use by ITU-T|ISO/IEC. general_tier_flag specifies the tier context for the interpretation of general_level_idc as specified. general_level_idc indicates a level to which OlsInScope conforms as specified. Bitstreams shall not contain values of general_level_idc other than those specified. Other values of general_level_idc are reserved for future use by ITU-T|ISO/IEC.

-   -   NOTE—A greater value of general_level_idc indicates a higher         level. The maximum level signalled in the DCI NAL unit for         OlsInScope may be higher than but cannot be lower than the level         signalled in the SPS for a CLVS contained within OlsInScope.     -   NOTE—When OlsInScope conforms to multiple profiles,         general_profile_idc should indicate the profile that provides         the preferred decoded result or the preferred bitstream         identification, as determined by the encoder (in a manner not         specified in this Specification).     -   NOTE—When the CVSs of OlsInScope conform to different profiles,         multiple profile_tier_level( ) syntax structures may be included         in the DCI NAL unit such that for each CVS of the OlsInScope         there is at least one set of indicated profile, tier, and level         for a decoder that is capable of decoding the CVS.         num_sub_profiles specifies the number of the         general_sub_profile_idc[i] syntax elements.         general_sub_profile_idc[i] indicates the i-th interoperability         metadata registered as specified by Rec. ITU-T T.35, the         contents of which are not specified in this Specification.         sublayer_level_present_flag[i] equal to 1 specifies that level         information is present in the profile_tier_level( ) syntax         structure for the sublayer representation with TemporalId equal         to i, sublayer_level_present_flag[i] equal to 0 specifies that         level information is not present in the profile_tier_level( )         syntax structure for the sublayer representation with TemporalId         equal to i.         ptl_alignment_zero_bits shall be equal to 0.         The semantics of the syntax element sublayer_level_idc[i] is,         apart from the specification of the inference of not present         values, the same as the syntax element general_level_idc, but         apply to the sublayer representation with TemporalId equal to i.         When not present, the value of sublayer_level_idc[i] is inferred         as follows:     -   sublayer_level_idc[maxNumSubLayersMinus1] is inferred to be         equal to general_level_idc of the same profile_tier_level( )         structure,     -   For i from maxNumSubLayersMinus1−1 to 0 (in decreasing order of         values of i), inclusive, sublayer_level_idc[i] is inferred to be         equal to sublayer_level_idc[i+1].

The signaling of profile, tier, level information (i.e. profile_tier_level( )) in the VPS in JVET-R2001 may be less than ideal. For example, the signaling of syntax element vps_num_ptls_minus1 may be unnecessary in some cases. That is, according to the techniques herein, syntax element vps_num_ptls_minus1 may not be signaled and its value may be inferred in some cases. This may result in bit savings in some cases.

FIG. 1 is a block diagram illustrating an example of a system that may be configured to code (i.e., encode and/or decode) video data according to one or more techniques of this disclosure. System 100 represents an example of a system that may encapsulate video data according to one or more techniques of this disclosure. As illustrated in FIG. 1, system 100 includes source device 102, communications medium 110, and destination device 120. In the example illustrated in FIG. 1, source device 102 may include any device configured to encode video data and transmit encoded video data to communications medium 110. Destination device 120 may include any device configured to receive encoded video data via communications medium 110 and to decode encoded video data. Source device 102 and/or destination device 120 may include computing devices equipped for wired and/or wireless communications and may include, for example, set top boxes, digital video recorders, televisions, desktop, laptop or tablet computers, gaming consoles, medical imagining devices, and mobile devices, including, for example, smartphones, cellular telephones, personal gaming devices.

Communications medium 110 may include any combination of wireless and wired communication media, and/or storage devices. Communications medium 110 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. Communications medium 110 may include one or more networks. For example, communications medium 110 may include a network configured to enable access to the World Wide Web, for example, the Internet. A network may operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include Digital Video Broadcasting (DVB) standards, Advanced Television Systems Committee (ATSC) standards, Integrated Services Digital Broadcasting (ISDB) standards, Data Over Cable Service Interface Specification (DOCSIS) standards, Global System Mobile Communications (GSM) standards, code division multiple access (CDMA) standards, 3rd Generation Partnership Project (3GPP) standards, European Telecommunications Standards Institute (ETSI) standards, Internet Protocol (IP) standards. Wireless Application Protocol (WAP) standards, and Institute of Electrical and Electronics Engineers (IEEE) standards.

Storage devices may include any type of device or storage medium capable of storing data. A storage medium may include a tangible or non-transitory computer-readable media. A computer readable medium may include optical discs, flash memory, magnetic memory, or any other suitable digital storage media. In some examples, a memory device or portions thereof may be described as non-volatile memory and in other examples portions of memory devices may be described as volatile memory. Examples of volatile memories may include random access memories (RAM), dynamic random access memories (DRAM), and static random access memories (SRAM). Examples of non-volatile memories may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. Storage device(s) may include memory cards (e.g., a Secure Digital (SD) memory card), internal/external hard disk drives, and/or internal/external solid state drives. Data may be stored on a storage device according to a defined file format.

FIG. 4 is a conceptual drawing illustrating an example of components that may be included in an implementation of system 100. In the example implementation illustrated in FIG. 4, system 100 includes one or more computing devices 402A-402N, television service network 404, television service provider site 406, wide area network 408, local area network 410, and one or more content provider sites 412A-412N. The implementation illustrated in FIG. 4 represents an example of a system that may be configured to allow digital media content, such as, for example, a movie, a live sporting event, etc., and data and applications and media presentations associated therewith to be distributed to and accessed by a plurality of computing devices, such as computing devices 402A-402N. In the example illustrated in FIG. 4, computing devices 402A-402N may include any device configured to receive data from one or more of television service network 404, wide area network 408, and/or local area network 410. For example, computing devices 402A-402N may be equipped for wired and/or wireless communications and may be configured to receive services through one or more data channels and may include televisions, including so-called smart televisions, set top boxes, and digital video recorders. Further, computing devices 402A-402N may include desktop, laptop, or tablet computers, gaming consoles, mobile devices, including, for example, “smart” phones, cellular telephones, and personal gaming devices.

Television service network 404 is an example of a network configured to enable digital media content, which may include television services, to be distributed. For example, television service network 404 may include public over-the-air television networks, public or subscription-based satellite television service provider networks, and public or subscription-based cable television provider networks and/or over the top or Internet service providers. It should be noted that although in some examples television service network 404 may primarily be used to enable television services to be provided, television service network 404 may also enable other types of data and services to be provided according to any combination of the telecommunication protocols described herein. Further, it should be noted that in some examples, television service network 404 may enable two-way communications between television service provider site 406 and one or more of computing devices 402A-402N. Television service network 404 may comprise any combination of wireless and/or wired communication media. Television service network 404 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. Television service network 404 may operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include DVB standards, ATSC standards, ISDB standards, DTMB standards, DMB standards. Data Over Cable Service Interface Specification (DOCSIS) standards, HbbTV standards, W3C standards, and UPnP standards.

Referring again to FIG. 4, television service provider site 406 may be configured to distribute television service via television service network 404. For example, television service provider site 406 may include one or more broadcast stations, a cable television provider, or a satellite television provider, or an Internet-based television provider. For example, television service provider site 406 may be configured to receive a transmission including television programming through a satellite uplink/downlink. Further, as illustrated in FIG. 4, television service provider site 406 may be in communication with wide area network 408 and may be configured to receive data from content provider sites 412A-412N. It should be noted that in some examples, television service provider site 406 may include a television studio and content may originate therefrom.

Wide area network 408 may include a packet based network and operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include Global System Mobile Communications (GSM) standards, code division multiple access (CDMA) standards, 3^(rd) Generation Partnership Project (3GPP) standards, European Telecommunications Standards Institute (ETSI) standards, European standards (EN), IP standards, Wireless Application Protocol (WAP) standards, and Institute of Electrical and Electronics Engineers (IEEE) standards, such as, for example, one or more of the IEEE 802 standards (e.g., Wi-Fi). Wide area network 408 may comprise any combination of wireless and/or wired communication media. Wide area network 408 may include coaxial cables, fiber optic cables, twisted pair cables. Ethernet cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. In one example, wide area network 408 may include the Internet. Local area network 410 may include a packet based network and operate according to a combination of one or more telecommunication protocols. Local area network 410 may be distinguished from wide area network 408 based on levels of access and/or physical infrastructure. For example, local area network 410 may include a secure home network.

Referring again to FIG. 4, content provider sites 412A-412N represent examples of sites that may provide multimedia content to television service provider site 406 and/or computing devices 402A-402N. For example, a content provider site may include a studio having one or more studio content servers configured to provide multimedia files and/or streams to television service provider site 406. In one example, content provider sites 412A-412N may be configured to provide multimedia content using the IP suite. For example, a content provider site may be configured to provide multimedia content to a receiver device according to Real Time Streaming Protocol (RTSP). HTTP, or the like. Further, content provider sites 412A-412N may be configured to provide data, including hypertext based content, and the like, to one or more of receiver devices computing devices 402A-402N and/or television service provider site 406 through wide area network 408. Content provider sites 412A-412N may include one or more web servers. Data provided by data provider site 412A-412N may be defined according to data formats.

Referring again to FIG. 1, source device 102 includes video source 104, video encoder 106, data encapsulator 107, and interface 108. Video source 104 may include any device configured to capture and/or store video data. For example, video source 104 may include a video camera and a storage device operably coupled thereto. Video encoder 106 may include any device configured to receive video data and generate a compliant bitstream representing the video data. A compliant bitstream may refer to a bitstream that a video decoder can receive and reproduce video data therefrom. Aspects of a compliant bitstream may be defined according to a video coding standard. When generating a compliant bitstream video encoder 106 may compress video data. Compression may be lossy (discernible or indiscernible to a viewer) or lossless. FIG. 5 is a block diagram illustrating an example of video encoder 500 that may implement the techniques for encoding video data described herein. It should be noted that although example video encoder 500 is illustrated as having distinct functional blocks, such an illustration is for descriptive purposes and does not limit video encoder 500 and/or sub-components thereof to a particular hardware or software architecture. Functions of video encoder 500 may be realized using any combination of hardware, firmware, and/or software implementations.

Video encoder 500 may perform intra prediction coding and inter prediction coding of picture areas, and, as such, may be referred to as a hybrid video encoder. In the example illustrated in FIG. 5, video encoder 500 receives source video blocks. In some examples, source video blocks may include areas of picture that has been divided according to a coding structure. For example, source video data may include macroblocks. CTUs. CBs, sub-divisions thereof, and/or another equivalent coding unit. In some examples, video encoder 500 may be configured to perform additional sub-divisions of source video blocks. It should be noted that the techniques described herein are generally applicable to video coding, regardless of how source video data is partitioned prior to and/or during encoding. In the example illustrated in FIG. 5, video encoder 500 includes summer 502, transform coefficient generator 504, coefficient quantization unit 506, inverse quantization and transform coefficient processing unit 508, summer 510, intra prediction processing unit 512, inter prediction processing unit 514, filter unit 516, and entropy encoding unit 518. As illustrated in FIG. 5, video encoder 500 receives source video blocks and outputs a bitstream.

In the example illustrated in FIG. 5, video encoder 500 may generate residual data by subtracting a predictive video block from a source video block. The selection of a predictive video block is described in detail below. Summer 502 represents a component configured to perform this subtraction operation. In one example, the subtraction of video blocks occurs in the pixel domain. Transform coefficient generator 504 applies a transform, such as a discrete cosine transform (DCT), a discrete sine transform (DST), or a conceptually similar transform, to the residual block or sub-divisions thereof (e.g., four 8×8 transforms may be applied to a 16×16 array of residual values) to produce a set of residual transform coefficients. Transform coefficient generator 504 may be configured to perform any and all combinations of the transforms included in the family of discrete trigonometric transforms, including approximations thereof. Transform coefficient generator 504 may output transform coefficients to coefficient quantization unit 506. Coefficient quantization unit 506 may be configured to perform quantization of the transform coefficients. The quantization process may reduce the bit depth associated with some or all of the coefficients. The degree of quantization may alter the rate-distortion (i.e., bit-rate vs. quality of video) of encoded video data. The degree of quantization may be modified by adjusting a quantization parameter (QP). A quantization parameter may be determined based on slice level values and/or CU level values (e.g., CU delta QP values). QP data may include any data used to determine a QP for quantizing a particular set of transform coefficients. As illustrated in FIG. 5, quantized transform coefficients (which may be referred to as level values) are output to inverse quantization and transform coefficient processing unit 508. Inverse quantization and transform coefficient processing unit 508 may be configured to apply an inverse quantization and an inverse transformation to generate reconstructed residual data. As illustrated in FIG. 5, at summer 510, reconstructed residual data may be added to a predictive video block. In this manner, an encoded video block may be reconstructed and the resulting reconstructed video block may be used to evaluate the encoding quality for a given prediction, transformation, and/or quantization. Video encoder 500 may be configured to perform multiple coding passes (e.g., perform encoding while varying one or more of a prediction, transformation parameters, and quantization parameters). The rate-distortion of a bitstream or other system parameters may be optimized based on evaluation of reconstructed video blocks. Further, reconstructed video blocks may be stored and used as reference for predicting subsequent blocks.

Referring again to FIG. 5, intra prediction processing unit 512 may be configured to select an intra prediction mode for a video block to be coded. Intra prediction processing unit 512 may be configured to evaluate a frame and determine an intra prediction mode to use to encode a current block. As described above, possible intra prediction modes may include planar prediction modes, DC prediction modes, and angular prediction modes. Further, it should be noted that in some examples, a prediction mode for a chroma component may be inferred from a prediction mode for a luma prediction mode. Intra prediction processing unit 512 may select an intra prediction mode after performing one or more coding passes. Further, in one example, intra prediction processing unit 512 may select a prediction mode based on a rate-distortion analysis. As illustrated in FIG. 5, intra prediction processing unit 512 outputs intra prediction data (e.g., syntax elements) to entropy encoding unit 518 and transform coefficient generator 504. As described above, a transform performed on residual data may be mode dependent (e.g., a secondary transform matrix may be determined based on a prediction mode).

Referring again to FIG. 5, inter prediction processing unit 514 may be configured to perform inter prediction coding for a current video block. Inter prediction processing unit 514 may be configured to receive source video blocks and calculate a motion vector for PUs of a video block. A motion vector may indicate the displacement of a prediction unit of a video block within a current video frame relative to a predictive block within a reference frame. Inter prediction coding may use one or more reference pictures. Further, motion prediction may be uni-predictive (use one motion vector) or bi-predictive (use two motion vectors). Inter prediction processing unit 514 may be configured to select a predictive block by calculating a pixel difference determined by, for example, sum of absolute difference (SAD), sum of square difference (SSD), or other difference metrics. As described above, a motion vector may be determined and specified according to motion vector prediction. Inter prediction processing unit 514 may be configured to perform motion vector prediction, as described above. Inter prediction processing unit 514 may be configured to generate a predictive block using the motion prediction data. For example, inter prediction processing unit 514 may locate a predictive video block within a frame buffer (not shown in FIG. 5). It should be noted that inter prediction processing unit 514 may further be configured to apply one or more interpolation filters to a reconstructed residual block to calculate sub-integer pixel values for use in motion estimation. Inter prediction processing unit 514 may output motion prediction data for a calculated motion vector to entropy encoding unit 518.

Referring again to FIG. 5, filter unit 516 receives reconstructed video blocks and coding parameters and outputs modified reconstructed video data. Filter unit 516 may be configured to perform deblocking and/or Sample Adaptive Offset (SAO) filtering. SAO filtering is a non-linear amplitude mapping that may be used to improve reconstruction by adding an offset to reconstructed video data. It should be noted that as illustrated in FIG. 5, intra prediction processing unit 512 and inter prediction processing unit 514 may receive modified reconstructed video block via filter unit 216. Entropy encoding unit 518 receives quantized transform coefficients and predictive syntax data (i.e., intra prediction data and motion prediction data). It should be noted that in some examples, coefficient quantization unit 506 may perform a scan of a matrix including quantized transform coefficients before the coefficients are output to entropy encoding unit 518. In other examples, entropy encoding unit 518 may perform a scan. Entropy encoding unit 518 may be configured to perform entropy encoding according to one or more of the techniques described herein. In this manner, video encoder 500 represents an example of a device configured to generate encoded video data according to one or more techniques of this disclosure.

Referring again to FIG. 1, data encapsulator 107 may receive encoded video data and generate a compliant bitstream, e.g., a sequence of NAL units according to a defined data structure. A device receiving a compliant bitstream can reproduce video data therefrom. Further, as described above, sub-bitstream extraction may refer to a process where a device receiving a ITU-T H.265 compliant bitstream forms a new ITU-T H.265 compliant bitstream by discarding and/or modifying data in the received bitstream. It should be noted that the term conforming bitstream may be used in place of the term compliant bitstream. In one example, data encapsulator 107 may be configured to generate syntax according to one or more techniques described herein. It should be noted that data encapsulator 107 need not necessary be located in the same physical device as video encoder 106. For example, functions described as being performed by video encoder 106 and data encapsulator 107 may be distributed among devices illustrated in FIG. 4.

As described above, the signaling of profile, tier, level information in the VPS in JVET-R2001 may be less than ideal. In one example, according to the techniques herein, syntax element vps_num_ptls_minus1 may not be signaled and its value may be inferred in some cases. That is, in one example, according to the techniques herein, syntax element vps_num_ptls_minus1 may be conditionally signaled only when syntax element vps_vmax_layers_minus1, which specifies the maximum allowed number of layers in each CVS referring to the VPS minus 1, is greater than 0. This saves one byte for the single layer case. The single layer case is a common case. That is, when vps_max_layers_minus1 is equal to 0, a CVS is a single layer CVS. In this case, only one profile tier level syntax structure is necessary to be signaled for the single layer. Thus, the number of signaled profile tier level syntax structure is known to be equal to 1 and does not need to be signaled.

Table 5 illustrates an example of the relevant portion of a video parameter set syntax structure where vps_num_ptls_minus1 is conditionally signaled according to the techniques herein.

TABLE 5 Descriptor video_parameter_set_rbsp( ) { vps_video_parameter_set_id u(4) vps_max_layers_minus1 u(6) vps_max_sublayers_minus1 u(3) if( vps_max_layers_minus1 > 0 && vps_max_sublayers_minus1 > 0 ) vps_all_layers_same_num_sublayers_flag u(1) if( vps_max_layers_minus1 > 0 ) vps_all_independent_layers_flag u(1) for( i = 0; i <= vps_max_layers_minus1; i++ ) { vps_layer_id[ i ] u(6) if( i > 0 && !vps_all_independent_layers_flag ) { vps_independent_layer_flag[ i ] u(1) if( !vps_independent_layer_flag[ i ] ) { max_tid_ref_present_flag[ i ] u(1) for( j = 0; j < i; j++ ) { vps_direct_ref_layer_flag[ i ][ j ] u(1) if( max_tid_ref_present_flag[ i ] && vps_direct_ref_layer_flag[ i ][ j ] ) max_tid_il_ref_pics_plus1[ i ][ j ] u(3) } } } } if( vps_max_layers_minus1 > 0 ) { if( vps_all_independent_layers_flag ) each_layer_is_an_ols_flag u(1) if( !each_layer_is_an_ols_flag ) { if( !vps_all_independent_layers_flag ) ols_mode_idc u(2) if( ols_mode_idc = = 2 ) { num_output_layer_sets_minus1 u(8) for( i = 1; i <= num_output_layer_sets_minus1; i ++) for( j = 0; j <= vps_max_layers_minus1; j++ ) ols_output_layer_flag[ i ][ j ] u(1) } } } if( vps_max_layers_minus1 > 0 ) vps_num_ptls_minus1 u(8) for( i = 0; i <= vps_num_ptls_minus1; i++ ) { if( i > 0 ) pt_present_flag[ i ] u(1) if( vps_max_sublayers_minus1 > 0 && !vps_all_layers_same_num_sublayer_flag ) ptl_max_temporal_id[ i ] u(3) } while( !byte_aligned( ) ) vps_ptl_alignment_zero_bit /* equal to 0 */ f(1) for(i = 0; i <= vps_num_ptls_minus1; i++ ) profile_tier_level( pt_present_flag[ i ], ptl_max_temporal_id[ i ] ) for( i = 0; i < TotalNumOlss; i++ ) if( vps_num_ptls_minus1 > 0 && vps_num_ptls_minus1 + 1 != TotalNumOlss ) ols_ptl_idx[ i ] u(8) ... }

Table 6 illustrates another example of the relevant portion of a video parameter set syntax structure where vps_num_ptls_minus1 is conditionally signaled according to the techniques herein.

TABLE 6 Descriptor video_parameter_set_rbsp( ) { vps_video_parameter_set_id u(4) vps_max_layers_minus1 u(6) vps_max sublayers_minus1 u(3) if( vps_max_layers_minus1 > 0 && vps_max_sublayers_minus1 > 0 ) vps_all_layers_same_num_sublayers_flag u(1) if( vps_max_layers_minus1 > 0 ) vps_all_independent_layers_flag u(1) for( i = 0; i <= vps_max_layers_minus1; i++ ) { vps_layer_id[ i ] u(6) if( i > 0 && !vps_all_independent_layers_flag ) { vps_independent_layer_flag[ i ] u(1) if( !vps_independent_layer_flag[ i ] ) { max_tid_ref_present_flag[ i ] u(1) for( j = 0; j < i; j++ ) { vps_direct_ref_layer_flag[ i ][ j ] u(1) if( max_tid_ref_present_flag[ i ] && vps_direct_ref_layer_flag[ i ][ j ] ) max_tid_il_ref_pics_plus1[ i ][ j ] u(3) } } } } if( vps_max_layers_minus1 > 0 ) { if( vps_all_independent_layers_flag ) each_layer_is_an_ols_flag u(1) if( !each_layer_is_an_ols_flag ) { if( !vps_all_independent_layers_flag ) ols_mode_idc u(2) if( ols_mode_idc = = 2 ) { num_output_layer_sets_minus1 u(8) for( i = 1; i <= num_output_layer_sets_minus1; i ++) for( j = 0; j <= vps_max_layers_minus1; j++ ) ols_output_layer_flag[ i ][ j ] u(1) } } vps_num_ptls_minus1 u(8) } for( i = 0; i <= vps_num_ptls_minus1; i++ ) { if( i > 0) pt_present_flag[ i ] u(1) if( vps_max_sublayers_minus1 > 0 && !vps_all_layers_same_num_sublayers_flag ) ptl_max_temporal_id[ i ] u(3) } while( !byte_aligned( ) ) vps_ptl_alignment_zero_bit /* equal to 0 */ f(1) for( i = 0; i <= vps_num_ptls_minus1; i++ ) profile_tier_level( pt_present_flag[ i ], ptl_max_temporal_id[ i ] ) for( i = 0; i < TotalNumOlss; i++ ) if( vps_num_ptls_minus1 > 0 && vps_num_ptls_minus1 + 1 != TotalNumOlss ) ols_ptl_idx[ i ] u(8) ... }

With respect to Table 5 and Table 6, the semantics may be based on the semantics provided above with the semantics for syntax element vps_num_ptls_minus1 based on the following:

vps_num_ptls_minus1 plus 1 specifies the number of profile_tier_level( ) syntax structures in the VPS. The value of vps_num_ptls_minus1 shall be less than TotalNumOlss. When not present vps_num_ptls_minus1 is inferred to be equal to 0. In one example, the value of vps_num_ptls_minus1 shall be in the range of 0 to TotalNumOlss−1, inclusive.

In one example, instead of the conditional signaling as above, a conformance constraint may be specified as follows:

It is a requirement of bitstream conformance that when vps_max_layers_minus1 is equal to 0 vps_num_ptls_minus1 shall be equal to 0.

In one example, according to the techniques herein, syntax element vps_num_output_layer_sets_minus1 may be instead be signaled using minus 2 coding, e.g., as vps_num_output_layer_sets_minus2. It is asserted that in JVET-R2001, vps_num_output_layer_sets_minus1 is signaled when vps_max_layers_minus1 is greater than 0 (and when vps_ols_mode_idc is equal to 2) and in this case, since the 0-th OLS has the lowest layer, there are at least two output layer sets. Thus, it is asserted that the number of output layer sets can be signaled with a minus 2 coding. Table 7 illustrates an example of the relevant portion of a video parameter set syntax structure according to the techniques herein.

TABLE 7 Descriptor video_parameter_set_rbsp( ) { vps_video_parameter_set_id u(4) vps_max_layers_minus1 u(6) vps_max_sublayers_minus1 u(3) if( vps_max_layers_minus1 > 0 && vps_max_sublayers_minus1 > 0 ) vps_all_layers_same_num_sublayers_flag u(1) if( vps_max_layers_minus1 > 0 ) vps_all_independent_layers_flag u(1) for( i = 0; i <= vps_max_layers_minus1; i++ ) { vps_layer_id[ i ] u(6) if( i > 0 && !vps_all_independent_layers_flag ) { vps_independent_layer_flag[ i ] u(1) if( !vps_independent_layer_flag[ i ] ) { max_tid_ref_present_flag[ i ] u(1) for( j = 0; j < i; j++ ) { vps_direct_ref_layer_flag[ i ][ j ] u(1) if( max_tid_ref_present_flag[ i ] && vps_direct_ref_layer_flag[ i ][ j ] ) max_tid_il_ref_pics_plus1[ i ][ j ] u(3) } } } } if( vps_max_layers_minus1 > 0 ) { if( vps_all_independent_layers_flag ) each_layer_is_an_ols_flag u(1) if( !each_layer_is_an_ols_flag ) { if( !vps_all_independent_layers_flag ) ols_mode_idc u(2) if( ols_mode_idc = = 2 ) { num_output_layer_sets_minus2 u(8) for( i = 1; i <= num_output_layer_sets_minus2 + 1; i ++) for( j = 0; j <= vps_max_layers_minus1; j++ ) ols_output_layer_flag[ i ][ j ] u(1) } } vps_num_ptls_minus1 u(8) } for( i = 0; i <= vps_num_ptls_minus1; i++ ) { if( i > 0 ) pt_present_flag[ i ] u(1) if( vps_max_sublayers_minus1 > 0 && !vps_all_layers_same_num_sublayers_flag ) ptl_max_temporal_id[ i ] u(3) } while( !byte_aligned( ) ) vps_ptl_alignment_zero_bit /* equal to 0 */ f(1) for( i = 0; i <= vps_num_ptls_minus1; i++ ) profile_tier_level( pt_present_flag[ i ], ptl_max_temporal_id[ i ] ) for( i = 0; i < TotalNumOlss; i++ ) if( vps_num_ptls_minus1 > 0 && vps_num_ptls_minus1 + 1 != TotalNumOlss ) ols_ptl_idx[ i ] u(8) ... }

With respect to Table 7, the semantics may be based on the semantics provided above with the semantics for syntax element num_output_layer_sets_minus2 based on the following:

num_output_layer_sets_minus2 plus 2 specifies the total number of OLSs specified by the VPS when ols_mode_ide is equal to 2. The variable olsModeIdc derived as follows:

if( !each_layer_is_an_ols_flag ) olsModeIdc = ols_mode_idc else olsModeIdc = 4 The variable TotalNumOlss, specifying the total number of OLSs specified by the VPS, is derived as follows:

if( vps_max_layers_minus1 = = 0 ) TotalNumOlss = 1 else if( olsModeIdc = = 4 | | olsModeIdc = = 0 | | olsModeIdc = = 1 ) TotalNumOlss = vps_max_layers_minus1 + 1 else if( vps_ols_mode_idc = = 2 ) TotalNumOlss = num_output_layer_sets_minus2 + 2 Alternatively a conformance constraint is proposed: It is a requirement of bitstream conformance that vps_num_output_layer_sets_minus1 shall be greater than 0.

It should be noted that in some typical cases (e.g., multi-view video) values of OLS DPB picture width, height, chroma format and bit depth may be the same for multiple OLSs. In one example, according to the techniques herein, a flag may be signaled for each multi-layer OLS to indicate if these values are the same as the values for the previous OLS. In one example, a flag may be signaled for each multi-layer OLS (except the 0-th—or first in order multilayer OLS) to indicate if OLS DPB picture width, height, chroma format and bit depth values are the same as the corresponding values for the previous OLS. This can save bits in common cases. Table 8 illustrates an example of a video parameter set syntax structure according to the techniques herein.

TABLE 8 Descriptor video_parameter_set_rbsp( ) { vps_video_parameter_set_id  u(4) vps_max_layers_minus1  u(6) vps_max_sublayers_minus1  u(3) if( vps_max_layers_minus1 > 0 && vps_max_sublayers_minus1 > 0 ) vps_all_layers_same_num_sublayers_flag  u(1) if( vps_max_layers_minus1 > 0 ) vps_all_independent_layers_flag  u(1) for( i = 0; i <= vps_max_layers_minus1; i++ ) { vps_layer_id[ i ]  u(6) if( i > 0 && !vps_all_independent_layers_flag ) { vps_independent_layer_flag[ i ]  u(1) if( !vps_independent_layer_flag[ i ] ) { vps_max_tid_ref_present_flag[ i ]  u(1) for( j = 0; j < i; j++ ) { vps_direct_ref_layer_flag[ i ][ j ]  u(1) if( vps_max_tid_ref_present_flag[ i ] && vps_direct_ref_layer_flag[ i ][j ] ) vps_max_tid_il_ref_pics_plus1[ i ][ j ]  u(3) } } } } if( vps_max_layers_minus1 > 0 ) { if( vps_all_independent_layers_flag ) vps_each_layer_is_an_ols_flag  u(1) if( !vps_each_layer_is_an_ols_flag ) { if( !vps_all_independent_layers_flag ) vps_ols_mode_idc  u(2) if( vps_ols_mode_idc = = 2 ) { vps_num_output_layer_sets_minus1  u(8) for( i = 1; i < vps_num_output_layer_sets_minus1; i++) for( j = 0; j <= vps_max_layers_minus1; j++ ) vps_ols_output_layer_flag[ i ][ j ]  u(1) } } } vps_num_ptls_(——)minus1  u(8) for( i = 0; i <= vps_num_ptls_minus1; i++ ) { if( i > 0 ) vps_pt_present_flag[ i ]  u(1) if( !vps_all_layers_same_num_sublayers_flag ) vps_ptl_max_temporal_id[ i ]  u(3) } while( !byte_aligned( ) ) vps_ptl_alignment_zero_bit /* equal to 0 */  f(1) for( i = 0; i <= vps_num_ptls_minus1; i++ ) profile_tier_level( vps_pt_present_flag[ i ], vps_ptl_max_temporal_id[ i ] ) for( i = 0; i < TotalNumOlss; i++ ) if( vps_num_ptls_minus1 > 0 && vps_num_prls_minus1 + 1 != TotalNumOlss ) vps_ols_ptl_idx[ i ]  u(8) if( !vps_each_layer_is_an_ols_flag ) { vps_num_dpb_params_minus1 ue(v) if( vps_max_sublayers_minus1 > 0 ) vps_sublayer_dpb_params_present_flag  u(1) for( i = 0; i < VpsNumDpbParams; i++ ) { if( !vps_all_layers_same_num_sublayers_flag ) vps_dpb_max_temporal_id[ i ]  u(3) dpb_parameters( vps_dpb_max_temporal_id[ i ], vps_sublayer_dpb_params_present_flag ) } for( i = 0; i < NumMultiLayerOlss; ) { if( i > 0 ) vps_ols_representation_format_info_signalled_flag[ i ]  u(1) if( vps_ols_representation_format_info_signalled_flag[ i ]) { vps_ols_dpb_pic_width[ i ] ue(v) vps_ols_dpb_pic_height[ i ] ue(v) vps_ols_dpb_chroma_format[ i ]]  u(2) vps_ols_dpb_bitdepth_minus8[ i ue(v) } if( VpsNumDpbParams > 1 && vps_num_dpb_params != NumMultiLayerOlss ) vps_ols_dpb_params_idx[ i ] ue(v) } vps_general_hrd_params_present_flag  u(1) } if( vps_general_hrd_params_present_flag ) { general_hrd_parameters( ) if( vps_max_sublayers_minus1 > 0 ) vps_sublayer_cpb_params_present_flag  u(1) vps_num_ols_hrd_params_minus1 ue(v) for( i = 0; i <= vps_num_ols_hrd_params_minus1; i++ ) { if( !vps_all_layers_same_num_sublayers_flag ) hrd_max_tid[ i ]  u(3) firstSubLayer = vps_sublayer_cpb_params_present_flag ? 0 : vps_hrd_max_tid[ i ] ols_hrd_parameters( firstSubLayer, vps_hrd_max_tid[ i ] ) } if( vps_num_ols_hrd_params_minus1 > 0 && vps_num_ols_hrd_params_minus1 + 1 != NumMultiLayerOlss ) for( i = 0; i < NumMultiLayerOlss; i++ ) vps_ols_hrd_idx[ i ] ue(v) } vps_extension_flag  u(1) if( vps_extension_flag ) while( more_rbsp_data( ) ) vps_extension_data_flag  u(1) rbsp_trailing_bits( ) }

With respect to Table 8, the semantics may be based on the semantics provided above and based on the following:

vps_ols_representation_format_info_signalled_flag[i] equal to 1 specifies that syntax elements vps_ols_dpb_pic_width[i], vps_ols_dpb_pic_height[i], vps_ols_dpb_chroma_format[i], and vps_ols_dpb_bitdepth_minus8[i] are signalled for the i-th OLS in the VPS. vps_ols_representation_format_info_signalled_flag[i] equal to 0 specifies that syntax elements vps_ols_dpb_pic_width[i], vps_ols_dpb_pic_height[i], vps_ols_dpb_chroma_format[i], and vps_ols_dpb_bitdepth_minus8[i] are not signalled for the i-th OLS in the VPS. The value of vps_ols_representation_format_info_signalled_flag[0] is inferred to be equal to 1. vps_ols_dpb_pic_width[i] specifies the width, in units of luma samples, of each picture storage buffer for the i-th multi-layer OLS. When not present vps_ols_dpb_pic_width[i] is inferred to be equal to vps_ols_dpb_pic_width[i−1]. vps_ols_dpb_pic_height[i] specifies the height, in units of luma samples, of each picture storage buffer for the i-th multi-layer OLS. When not present vps_ols_dpb_pic_height[i] is inferred to be equal to vps_ols_dpb_pic_height[i−1]. vps_ols_dpb_chroma_format[i] specifies the greatest allowed value of sps_chroma_format_idc for all SPSs that are referred to by CLVSs in the CVS for the i-th multi-layer OLS. When not present vps_ols_dpb_chroma_format[i] is inferred to be equal to vps_ols_dpb_chroma_format[i−1]. vps_ols_dph_bitdepth_minus8[i] specifies the greatest allowed value of sps_bit_depth_minus8 for all SPSs that are referred to by CLVSs in the CVS for the i-th multi-layer OLS. When not present vps_ols_dpb_bitdepth_minus8[i] is inferred to be equal to vps_ols_dpb_bitdepth_minus8[i−1].

-   -   NOTE—For decoding the i-th multi-layer OLS, the decoder can         safely allocate memory for the DPB according to the values of         the syntax elements vps_ols_dpb_pic_width[i],         vps_ols_dpb_pic_height[i], vps_ols_dpb_chroma_format[i], and         vps_ols_dpb_bitdepth_minus8[i].         It should be noted that:         When vps_ols_representation_format_info_signalled_flag[i] is         equal to 0, the values of vps_ols_dpb_pic_width[i],         vps_ols_dpb_pic_height[i], vps_ols_dpb_chroma_format[i], and         vps_ols_dpb_bitdepth_minus8[i] are inferred to be the same as         the values of vps_ols_dpb_pic_width[i−1],         vps_ols_dpb_pic_height[i−1], vps_ols_dpb_chroma_format[i−1], and         vps_ols_dpb_bitdepth_minus8[i−1], respectively.

In this manner, source device 102 represents an example of a device configured to signal a syntax element in a video parameter set syntax structure specifying a maximum allowed number of layers in each coded video sequence referring to the video parameter set and conditionally signal a syntax element specifying a number of profile tier level syntax structures in the video parameter set based on the value of the maximum allowed number of layers.

Referring again to FIG. 1, interface 108 may include any device configured to receive data generated by data encapsulator 107 and transmit and/or store the data to a communications medium. Interface 108 may include a network interface card, such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can send and/or receive information. Further, interface 108 may include a computer system interface that may enable a file to be stored on a storage device. For example, interface 108 may include a chipset supporting Peripheral Component Interconnect (PCI) and Peripheral Component Interconnect Express (PCIe) bus protocols, proprietary bus protocols, Universal Serial Bus (USB) protocols, I²C. or any other logical and physical structure that may be used to interconnect peer devices.

Referring again to FIG. 1, destination device 120 includes interface 122, data decapsulator 123, video decoder 124, and display 126. Interface 122 may include any device configured to receive data from a communications medium. Interface 122 may include a network interface card, such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can receive and/or send information. Further, interface 122 may include a computer system interface enabling a compliant video bitstream to be retrieved from a storage device. For example, interface 122 may include a chipset supporting PCI and PCIe bus protocols, proprietary bus protocols. USB protocols, I²C. or any other logical and physical structure that may be used to interconnect peer devices. Data decapsulator 123 may be configured to receive and parse any of the example syntax structures described herein.

Video decoder 124 may include any device configured to receive a bitstream (e.g., a sub-bitstream extraction) and/or acceptable variations thereof and reproduce video data therefrom. Display 126 may include any device configured to display video data. Display 126 may comprise one of a variety of display devices such as a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display. Display 126 may include a High Definition display or an Ultra High Definition display. It should be noted that although in the example illustrated in FIG. 1, video decoder 124 is described as outputting data to display 126, video decoder 124 may be configured to output video data to various types of devices and/or sub-components thereof. For example, video decoder 124 may be configured to output video data to any communication medium, as described herein.

FIG. 6 is a block diagram illustrating an example of a video decoder that may be configured to decode video data according to one or more techniques of this disclosure (e.g., the decoding process for reference-picture list construction described above). In one example, video decoder 600 may be configured to decode transform data and reconstruct residual data from transform coefficients based on decoded transform data. Video decoder 600 may be configured to perform intra prediction decoding and inter prediction decoding and, as such, may be referred to as a hybrid decoder. Video decoder 600 may be configured to parse any combination of the syntax elements described above in Tables 1-8. Video decoder 600 may decode a picture based on or according to the processes described above, and further based on parsed values in Tables 1-8.

In the example illustrated in FIG. 6, video decoder 600 includes an entropy decoding unit 602, inverse quantization unit 604, inverse transform coefficient processing unit 606, intra prediction processing unit 608, inter prediction processing unit 610, summer 612, post filter unit 614, and reference buffer 616. Video decoder 600 may be configured to decode video data in a manner consistent with a video coding system. It should be noted that although example video decoder 600 is illustrated as having distinct functional blocks, such an illustration is for descriptive purposes and does not limit video decoder 600 and/or sub-components thereof to a particular hardware or software architecture. Functions of video decoder 600 may be realized using any combination of hardware, firmware, and/or software implementations.

As illustrated in FIG. 6, entropy decoding unit 602 receives an entropy encoded bitstream. Entropy decoding unit 602 may be configured to decode syntax elements and quantized coefficients from the bitstream according to a process reciprocal to an entropy encoding process. Entropy decoding unit 602 may be configured to perform entropy decoding according any of the entropy coding techniques described above. Entropy decoding unit 602 may determine values for syntax elements in an encoded bitstream in a manner consistent with a video coding standard. As illustrated in FIG. 6, entropy decoding unit 602 may determine a quantization parameter, quantized coefficient values, transform data, and prediction data from a bitstream. In the example, illustrated in FIG. 6, inverse quantization unit 604 and inverse transform coefficient processing unit 606 receive a quantization parameter, quantized coefficient values, transform data, and prediction data from entropy decoding unit 602 and outputs reconstructed residual data.

Referring again to FIG. 6, reconstructed residual data may be provided to summer 612. Summer 612 may add reconstructed residual data to a predictive video block and generate reconstructed video data. A predictive video block may be determined according to a predictive video technique (i.e., intra prediction and inter frame prediction). Intra prediction processing unit 608 may be configured to receive intra prediction syntax elements and retrieve a predictive video block from reference buffer 616. Reference buffer 616 may include a memory device configured to store one or more frames of video data. Intra prediction syntax elements may identify an intra prediction mode, such as the intra prediction modes described above. Inter prediction processing unit 610 may receive inter prediction syntax elements and generate motion vectors to identify a prediction block in one or more reference frames stored in reference buffer 616. Inter prediction processing unit 610 may produce motion compensated blocks, possibly performing interpolation based on interpolation filters. Identifiers for interpolation filters to be used for motion estimation with sub-pixel precision may be included in the syntax elements. Inter prediction processing unit 610 may use interpolation filters to calculate interpolated values for sub-integer pixels of a reference block. Post filter unit 614 may be configured to perform filtering on reconstructed video data. For example, post filter unit 614 may be configured to perform deblocking and/or Sample Adaptive Offset (SAO) filtering, e.g., based on parameters specified in a bitstream. Further, it should be noted that in some examples, post filter unit 614 may be configured to perform proprietary discretionary filtering (e.g., visual enhancements, such as, mosquito noise reduction). As illustrated in FIG. 6, a reconstructed video block may be output by video decoder 600. In this manner, video decoder 600 represents an example of a device configured parse a syntax element in a video parameter set syntax structure specifying a maximum allowed number of layers in each coded video sequence referring to the video parameter set and conditionally parse a syntax element specifying a number of profile tier level syntax structures in the video parameter set based on the value of the maximum allowed number of layers.

In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium.

By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but are instead directed to non-transitory, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor.” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements.

The techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs (e.g., a chip set). Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require realization by different hardware units. Rather, as described above, various units may be combined in a codec hardware unit or provided by a collection of interoperative hardware units, including one or more processors as described above, in conjunction with suitable software and/or firmware.

Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned embodiments may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

Various examples have been described. These and other examples are within the scope of the following claims. 

What is claimed is:
 1. A method of decoding video data, the method comprising: receiving a video parameter set; parsing a first syntax element in the video parameter set, wherein the first syntax element plus one specifies a maximum allowed number of layers in each coded video sequence referring to the video parameter set; and parsing a second syntax element in the video parameter set, in a case that a value of the first syntax element is greater than a threshold value, wherein the second syntax element plus one specifies a number of profile tier level syntax structure in the video parameter set.
 2. The method of claim 1, further comprising: parsing a third syntax element in the video parameter set, wherein the third syntax element plus two specifies a total number of output layer sets specified by the video parameter set.
 3. A device comprising one or more processors configured to: receive a video parameter set; parse a first syntax element in the video parameter set, wherein the first syntax element plus one specifies a maximum allowed number of layers in each coded video sequence referring to the video parameter set; and parse a second syntax element in the video parameter set, in a case that a value of the first syntax element is greater than a threshold value, wherein the second syntax element plus one specifies a number of profile tier level syntax structure in the video parameter set.
 4. A method of encoding image data, the method comprising: signaling a video parameter set, wherein: the video parameter set includes (i) a first syntax element, wherein the first syntax element plus one specifies a maximum allowed number of layers in each coded video sequence referring to the video parameter set and (ii) a second syntax element, wherein the second syntax element plus one specifies a number of profile tier level syntax structure in the video parameter set, and the second syntax element is included, in a case that a value of the first syntax element is greater than a threshold value. 